Sets our main struct and passes it to the parent class.
Creates a #SoupSession with the default options.
Cancels all pending requests in @session and closes all idle persistent connections.
Adds @feature's functionality to @session. You can also add a feature to the session at construct time by using the %SOUP_SESSION_ADD_FEATURE property.
If @feature_type is the type of a class that implements #SoupSessionFeature, this creates a new feature of that type and adds it to @session as with soup_session_add_feature(). You can use this when you don't need to customize the new feature in any way.
Emitted when the session requires authentication. If credentials are available call soup_auth_authenticate() on @auth. If these credentials fail, the signal will be emitted again, with @retrying set to %TRUE, which will continue until you return without calling soup_auth_authenticate() on @auth.
Emitted when a new connection is created. This is an internal signal intended only to be used for debugging purposes, and may go away in the future.
Emitted when a request is queued on @session. (Note that "queued" doesn't just mean soup_session_queue_message(); soup_session_send_message() implicitly queues the message as well.)
Emitted just before a request is sent. See #SoupSession::request_queued for a detailed description of the message lifecycle within a session.
Emitted when a request is removed from @session's queue, indicating that @session is done with it. See #SoupSession::request_queued for a detailed description of the message lifecycle within a session.
Emitted when an SSL tunnel is being created on a proxy connection. This is an internal signal intended only to be used for debugging purposes, and may go away in the future.
Causes @session to immediately finish processing @msg (regardless of its current state) with a final status_code of @status_code. You may call this at any time after handing @msg off to @session; if @session has started sending the request but has not yet received the complete response, then it will close the request's connection. Note that with requests that have side effects (eg, <literal>POST</literal>, <literal>PUT</literal>, <literal>DELETE</literal>) it is possible that you might cancel the request after the server acts on it, but before it returns a response, leaving the remote resource in an unknown state.
Start a connection to @uri. The operation can be monitored by providing a @progress_callback and finishes when the connection is done or an error ocurred.
Gets the #GIOStream created for the connection to communicate with the server.
Gets @session's #SoupSession:async-context. This does not add a ref to the context, so you will need to ref it yourself if you want it to outlive its session.
Gets the first feature in @session of type @feature_type. For features where there may be more than one feature of a given type, use soup_session_get_features().
Gets the first feature in @session of type @feature_type, provided that it is not disabled for @msg. As with soup_session_get_feature(), this should only be used for features where @feature_type is only expected to match a single feature. In particular, if there are two matching features, and the first is disabled on @msg, and the second is not, then this will return %NULL, not the second feature.
Generates a list of @session's features of type @feature_type. (If you want to see all features, you can pass %SOUP_TYPE_SESSION_FEATURE for @feature_type.)
Get the main Gtk struct
the main Gtk struct as a void*
Tests if @session has at a feature of type @feature_type (which can be the type of either a #SoupSessionFeature, or else a subtype of some class managed by another feature, such as #SoupAuth or #SoupRequest).
Pauses HTTP I/O on @msg. Call soup_session_unpause_message() to resume I/O.
Tells @session that an URI from the given @hostname may be requested shortly, and so the session can try to prepare by resolving the domain name in advance, in order to work more quickly once the URI is actually requested.
Tells @session that @uri may be requested shortly, and so the session can try to prepare (resolving the domain name, obtaining proxy address, etc.) in order to work more quickly once the URI is actually requested.
Queues the message @msg for asynchronously sending the request and receiving a response in the current thread-default #GMainContext. If @msg has been processed before, any resources related to the time it was last sent are freed.
Updates @msg's URI according to its status code and "Location" header, and requeues it on @session. Use this when you have set %SOUP_MESSAGE_NO_REDIRECT on a message, but have decided to allow a particular redirection to occur, or if you want to allow a redirection that #SoupSession will not perform automatically (eg, redirecting a non-safe method such as DELETE).
Removes @feature's functionality from @session.
Removes all features of type @feature_type (or any subclass of @feature_type) from @session. You can also remove standard features from the session at construct time by using the %SOUP_SESSION_REMOVE_FEATURE_BY_TYPE property.
Creates a #SoupRequest for retrieving @uri_string.
Creates a #SoupRequest for retrieving @uri_string, which must be an "http" or "https" URI (or another protocol listed in @session's #SoupSession:http-aliases or #SoupSession:https-aliases).
Creates a #SoupRequest for retrieving @uri, which must be an "http" or "https" URI (or another protocol listed in @session's #SoupSession:http-aliases or #SoupSession:https-aliases).
Creates a #SoupRequest for retrieving @uri.
This causes @msg to be placed back on the queue to be attempted again.
Synchronously sends @msg and waits for the beginning of a response. On success, a #GInputStream will be returned which you can use to read the response body. ("Success" here means only that an HTTP response was received and understood; it does not necessarily mean that a 2xx class status code was received.)
Asynchronously sends @msg and waits for the beginning of a response. When @callback is called, then either @msg has been sent, and its response headers received, or else an error has occurred. Call soup_session_send_finish() to get a #GInputStream for reading the response body.
Gets the response to a soup_session_send_async() call and (if successful), returns a #GInputStream that can be used to read the response body.
Synchronously send @msg. This call will not return until the transfer is finished successfully or there is an unrecoverable error.
"Steals" the HTTP connection associated with @msg from @session. This happens immediately, regardless of the current state of the connection, and @msg's callback will not be called. You can steal the connection from a #SoupMessage signal handler if you need to wait for part or all of the response to be received first.
Resumes HTTP I/O on @msg. Use this to resume after calling soup_session_pause_message().
Asynchronously creates a #SoupWebsocketConnection to communicate with a remote server.
Gets the #SoupWebsocketConnection response to a soup_session_websocket_connect_async() call and (if successful), returns a #SoupWebsocketConnection that can be used to communicate with the server.
Checks if @msg contains a response that would cause @session to redirect it to a new URL (ignoring @msg's %SOUP_MESSAGE_NO_REDIRECT flag, and the number of times it has already been redirected).
the main Gtk struct
#SoupSession is the object that controls client-side HTTP. A #SoupSession encapsulates all of the state that libsoup is keeping on behalf of your program; cached HTTP connections, authentication information, etc. It also keeps track of various global options and features that you are using.
Most applications will only need a single #SoupSession; the primary reason you might need multiple sessions is if you need to have multiple independent authentication contexts. (Eg, you are connecting to a server and authenticating as two different users at different times; the easiest way to ensure that each #SoupMessage is sent with the authentication information you intended is to use one session for the first user, and a second session for the other user.)
In the past, #SoupSession was an abstract class, and users needed to choose between #SoupSessionAsync (which always uses #GMainLoop<!-- -->-based I/O), or #SoupSessionSync (which always uses blocking I/O and can be used from multiple threads simultaneously). This is no longer necessary; you can (and should) use a plain #SoupSession, which supports both synchronous and asynchronous use. (When using a plain #SoupSession, soup_session_queue_message() behaves like it traditionally did on a #SoupSessionAsync, and soup_session_send_message() behaves like it traditionally did on a #SoupSessionSync.)
Additional #SoupSession functionality is provided by #SoupSessionFeature objects, which can be added to a session with soup_session_add_feature() or soup_session_add_feature_by_type() (or at construct time with the %SOUP_SESSION_ADD_FEATURE_BY_TYPE pseudo-property). For example, #SoupLogger provides support for logging HTTP traffic, #SoupContentDecoder provides support for compressed response handling, and #SoupContentSniffer provides support for HTML5-style response body content sniffing. Additionally, subtypes of #SoupAuth and #SoupRequest can be added as features, to add support for additional authentication and URI types.
All #SoupSessions are created with a #SoupAuthManager, and support for %SOUP_TYPE_AUTH_BASIC and %SOUP_TYPE_AUTH_DIGEST. For #SoupRequest types, #SoupRequestHTTP, #SoupRequestFile, and #SoupRequestData are supported. Additionally, sessions using the plain #SoupSession class (rather than one of its deprecated subtypes) have a #SoupContentDecoder by default.