SoupMessageFlags

The session should not follow redirect (3xx) responses received by this message.

The caller will rebuild the request body if the message is restarted; see soup_message_body_set_accumulate() for more details.

Deprecated: equivalent to calling soup_message_body_set_accumulate() on the incoming message body (ie, #SoupMessage:response_body for a client-side request), passing %FALSE.

Set by #SoupContentDecoder to indicate that it has removed the Content-Encoding on a message (and so headers such as Content-Length may no longer accurately describe the body).

if set after an https response has been received, indicates that the server's SSL certificate is trusted according to the session's CA.

Requests that the message should be sent on a newly-created connection, not reusing an existing persistent connection. Note that messages with non-idempotent #SoupMessage:method<!-- -->s behave this way by default, unless #SOUP_MESSAGE_IDEMPOTENT is set.

The message is considered idempotent, regardless its #SoupMessage:method, and allows reuse of existing idle connections, instead of always requiring a new one, unless #SOUP_MESSAGE_NEW_CONNECTION is set.

Request that a new connection is created for the message if there aren't idle connections available and it's not possible to create new connections due to any of the connection limits has been reached. If a dedicated connection is eventually created for this message, it will be dropped when the message finishes. Since 2.50

The #SoupAuthManager should not use the credentials cache for this message, neither to use cached credentials to automatically authenticate this message nor to cache the credentials after the message is successfully authenticated. This applies to both server and proxy authentication. Note that #SoupSession::authenticate signal will be emitted, if you want to disable authentication for a message use soup_message_disable_feature() passing #SOUP_TYPE_AUTH_MANAGER instead. Since 2.58