diff options
| author | Patrick Griffis <pgriffis@igalia.com> | 2020-10-28 13:33:07 -0500 |
|---|---|---|
| committer | Patrick Griffis <pgriffis@igalia.com> | 2020-10-28 13:37:57 -0500 |
| commit | e7a0f8e06f7cd4a9e66cf672fcedd234b26f1541 (patch) | |
| tree | f1c3f0d7ebcc3074cf297d4d4aab8981b1eada9d | |
| parent | f036244eb2c0c50291f5bf06cd1561d4310ce7c0 (diff) | |
| download | libsoup-e7a0f8e06f7cd4a9e66cf672fcedd234b26f1541.tar.gz | |
docs: Fixes for SoupMessage changes
| -rw-r--r-- | docs/reference/libsoup-3.0-sections.txt | 6 | ||||
| -rw-r--r-- | libsoup/soup-message-body.c | 15 |
2 files changed, 8 insertions, 13 deletions
diff --git a/docs/reference/libsoup-3.0-sections.txt b/docs/reference/libsoup-3.0-sections.txt index 6a664268..208ee8ba 100644 --- a/docs/reference/libsoup-3.0-sections.txt +++ b/docs/reference/libsoup-3.0-sections.txt @@ -14,6 +14,12 @@ soup_message_set_http_version soup_message_get_http_version soup_message_get_uri soup_message_set_uri +soup_message_get_method +soup_message_get_status +soup_message_get_reason_phrase +<SUBSECTION> +soup_message_get_request_headers +soup_message_get_response_headers <SUBSECTION> soup_message_set_status soup_message_set_status_full diff --git a/libsoup/soup-message-body.c b/libsoup/soup-message-body.c index 82c6b887..87e583f3 100644 --- a/libsoup/soup-message-body.c +++ b/libsoup/soup-message-body.c @@ -93,22 +93,11 @@ soup_message_body_new (void) * after the body is fully sent/received, and the chunks that make up * @body may be discarded when they are no longer needed. * - * In particular, if you set this flag to %FALSE on an "incoming" - * message body (that is, the #SoupMessage:response_body of a - * client-side message, or #SoupMessage:request_body of a server-side - * message), this will cause each chunk of the body to be discarded - * after its corresponding #SoupMessage::got_chunk signal is emitted. - * - * If you set this flag to %FALSE on the #SoupMessage:response_body of - * a server-side message, it will cause each chunk of the body to be - * discarded after its corresponding #SoupMessage::wrote_chunk signal - * is emitted. - * - * If you set the flag to %FALSE on the #SoupMessage:request_body of a + * If you set the flag to %FALSE on the #SoupMessage request_body of a * client-side message, it will block the accumulation of chunks into * @body's %data field, but it will not normally cause the chunks to * be discarded after being written like in the server-side - * #SoupMessage:response_body case, because the request body needs to + * #SoupMessage response_body case, because the request body needs to * be kept around in case the request needs to be sent a second time * due to redirection or authentication. However, if you set the * %SOUP_MESSAGE_CAN_REBUILD flag on the message, then the chunks will |