Age | Commit message (Collapse) | Author | Files | Lines |
|
Clients can specify a priority for each message added to the SoupSession,
which will determine the order in which it is processed by the
session's message processing queue.
https://bugzilla.gnome.org/show_bug.cgi?id=696277
|
|
|
|
SoupRequestHTTP is now implemented in terms of SoupSession SoupMessage
operations, so we might as well just expose those directly, for people
who want streaming APIs, but not SoupRequest.
|
|
GNOME_MAINTAINER_MODE_DEFINES apparently sets
LIBSOUP_DISABLE_DEPRECATED, which is now causing various jhbuild
modules to break. "Fix" this by renaming the define (which is only
still there because gtk-doc complains if it's not). The *right* way to
get deprecation warnings/errors now is to define
SOUP_VERSION_MIN_REQUIRED.
|
|
Add soup_auth_manager_use_auth(), for "preloading" authentication, and
make the old automatically-request-NTLM behavior happen only for
the legacy SoupSession subclasses.
|
|
|
|
Add a new SoupConnectionAuth class to help with connection tracking,
and make SoupAuthNTLM a subclass of it. Allow a single SoupAuthNTLM to
carry state information about multiple connections.
Make SoupSession store the SoupConnection a SoupMessage is associated
with on the message, and use that from SoupConnectionAuth rather than
tracking sockets by hand like SoupAuthManager had previously done.
Remove the connection tracking in SoupAuthManager, since it is no
longer needed.
|
|
Update the docs to reflect the changes in plain SoupSessions vs its
traditional subclasses. And while we're there, add a few new ones
(including making soup_session_queue_message() and
soup_session_send_message() work on plain SoupSession.
|
|
SoupMessage isn't being deprecated, and mirroring its API onto
SoupRequestHTTP is just going to result in always having to add every
new API twice. Also, it turns out to be less useful than originally
expected anyway, since you end up having to cast between SoupRequest
and SoupRequestHTTP frequently anyway.
This reverts commit d7117329400e47d2187ed033099d921d555f8d71 and most of
commit 53c270d0e2868fa5ad48ce864f10a9486b11a071.
|
|
gtk-doc expects "Deprecated:" notes in docs to be matched up with some
deprecation-guard #define. So even though we don't want people to use
it any more, add LIBSOUP_DISABLE_DEPRECATED back.
|
|
|
|
|
|
Since everything in libsoup-gnome is now deprecated and undocumented,
don't depend on it when building docs.
https://bugzilla.gnome.org/show_bug.cgi?id=573685
|
|
There's no real reason to use SoupProxyResolverGNOME rather than
SoupProxyResolverDefault, so deprecate that too.
libsoup-gnome now consists entirely of deprecated functions.
|
|
Move SoupCookieJarSqlite (and its sqlite3 dependency) into libsoup
from libsoup-gnome, but rename it to SoupCookieJarDB so libsoup-gnome
can keep using the old name. SoupCookieJarSqlite is now just a
wrapper around SoupCookieJarDB.
|
|
Add SoupSession helpers to return SoupRequestHTTP directly and allow
overriding the request method.
|
|
Add soup_request_disable_feature(), which proxies to
soup_message_disable_feature() for SoupRequestHTTP and is a no-op
otherwise.
Add SoupRequest tests to sniffing-test, which also tests
soup_request_disable_feature() now.
|
|
When dealing with SoupMessage-related signals in SoupRequest-using
code, it's useful to be able to get the message's associated
SoupRequest.
|
|
Mirror various SoupMessage-related API onto SoupRequestHTTP so that
you don't need to resort to soup_request_http_get_message().
|
|
Add soup_session_request() and soup_session_request_uri(),
implementing basically the same behavior as soup_requester_request()
and soup_requester_request_uri() (but without requiring a separate
SoupSessionFeature), and remove the unstable-api ifdefs from
soup-request*.h.
SoupRequester still exists, but it is still guarded by the
unstable-api ifdefs, and is just a dummy wrapper around the
functionality that is now in SoupSession.
|
|
|
|
Add SOUP_VERSION_X_XX, SOUP_VERSION_MIN_REQUIRED, and
SOUP_VERSION_MAX_ALLOWED, to enable version-based warnings.
Tag all functions with appropriate SOUP_AVAILABLE_IN_ and
SOUP_DEPRECATED_IN_ macros.
Also, fix up some "Since" tags to not refer to unstable releases or
non-.0 point releases.
|
|
Expose API to get information about the soup version. This is useful
because it allows applications to use API without actually depending on
it completely.
https://bugzilla.gnome.org/show_bug.cgi?id=684514
|
|
GFile already supports gresource when using g_file_new_for_uri() with a
resource:// URI. We can add "resource" as a valid scheme for
SoupRequestFile and make sure the GFile is created with the gresource
URI for gresource requests.
https://bugzilla.gnome.org/show_bug.cgi?id=682721
|
|
SoupMultipartInputStream can be used by the API user to wrap the input
stream, and provides API to obtain the next part and its headers,
using a SoupFilterInputStream internally for buffer management.
https://bugzilla.gnome.org/show_bug.cgi?id=656684
|
|
The soup_tld_* set of functions along with the list of public suffixes
published in http://publicsuffix.org allows API clients to get the base
domain of a given hostname or to check if a given domain is a public suffix
(one under which internet users can register new names).
https://bugzilla.gnome.org/show_bug.cgi?id=673802
|
|
that takes a SoupCookie in argument
Currently, the only way to add a cookie while checking first_party is to use
soup_cookie_jar_set_cookie_with_first_party(). However, this function takes an
unparsed cookie in argument.
In the event the client has already parsed the cookie (e.g. to do some
pre-processing), it would be useful to have an alternative to
soup_cookie_jar_set_cookie_with_first_party() which takes a parsed SoupCookie
in argument. This would be more efficient.
|
|
GSList of SoupCookies
Adds a soup_cookie_jar_get_cookie_list() function that returns the
cookies in the jar that would be sent with a request to a specific
uri, as a GSList of SoupCookies.
|
|
This new method will return a GBytes instance containing the
contents of the SoupBuffer.
https://bugzilla.gnome.org/show_bug.cgi?id=676776
|
|
It allows to query whether cookies are stored persisently by the
SoupCookieJar.
https://bugzilla.gnome.org/show_bug.cgi?id=672838
|
|
|
|
This deprecates soup_session_prepare_for_uri(). It basically does the same,
i.e., it lets the session prepare for a possible upcoming request by doing
DNS resolution. It additionally has cancellation support and adds a callback
to notify the caller when the operation finishes.
https://bugs.webkit.org/show_bug.cgi?id=41630
|
|
|
|
|
|
Currently SoupSession treats all URI schemes except "https" as aliases
for "http", and some apps depend on this. (Eg, iTunes sometimes
returns redirects involving "daap" URIs, which Rhythmbox needs to
treat as "http".) Unfortunately, this also means that it mishandles
redirects to, eg, ftp.
The http-aliases and https-aliases properties allow an app to
explicitly indicate which URI schemes should be considered aliases for
http and https, with other schemes considered to be unknown and
unhandled.
|
|
|
|
Patch from Davide Italiano
https://bugzilla.gnome.org/show_bug.cgi?id=650526
|
|
Patch from "arno"
https://bugzilla.gnome.org/show_bug.cgi?id=648948
|
|
modify SoupProxyResolverDefault so it's possible to override the
choice of g_proxy_resolver_get_default(), and make
SoupProxyResolverGNOME just be a subclass of SoupProxyResolverDefault
that specifically requests the "gnome" GProxyResolver.
libsoup-gnome no longer depends on libproxy and GConf. (Perhaps it
should now depend on gsettings-desktop-schemas, or else a
glib-networking that includes GProxyResolverGnome. But it will fall
back to using the libproxy-based proxy resolver in that case anyway,
so it's all good.)
https://bugzilla.gnome.org/show_bug.cgi?id=625898
|
|
- Detect gobject-introspection (g-i) in configure, using the M4 macro
from the newly-added introspection.m4. This adds
gobject-introspection as a new *optional* build dependency.
- Integrate the generation of .gir and .typelib files into the build
build process.
- Add the annotations from gir-repository to the source code.
- Include annotation glossary in "Reference Manual" main file.
See <https://bugzilla.gnome.org/show_bug.cgi?id=576595>.
|
|
|
|
Pointed out by Dominik Bylica
|
|
|
|
|
|
- Add -I$(top_builddir) to documentation scanner CFLAGS (fixes "make
distcheck" run from an out-of-tree build)
|
|
* libsoup/soup-message-headers.c (soup_message_headers_get_one)
(soup_message_headers_get_list): New replacements for
soup_message_headers_get(), indicating explicitly whether the
caller expects the header to be a list or not; for non-list-type
headers, if there's more than one, the second one should be
ignored rather than concatenated to the first.
(soup_message_headers_get): deprecate this.
* libsoup/*.c:
* tests/*.c: Update to use soup_message_headers_get_one() or
_get_list() as appropriate.
* tests/header-parsing.c (do_content_type_tests): Add some tests
of Content-Type parsing/setting, including making sure that
duplicate Content-Type headers are ignored.
* docs/reference/libsoup-2.4-sections.txt: update
svn path=/trunk/; revision=1258
|
|
* docs/reference/client-howto.xml: clarify that SoupSessionAsync
is not thread-safe, and that setting a non-default GMainContext on
a non-threadsafe object means you can only use that object from
that GMainContext's thread.
svn path=/trunk/; revision=1255
|
|
g_hash_table_lookup().
As currently written, libproxy's gnome plugin causes intermittent
gvfsd-http crashes, and I didn't have time to come up with either
a fix or a workaround. So for 2.26.0 we will fall back to using
the GConf-based proxy resolver. Hopefully to be fixed for 2.26.1.
* configure.in: require both gconf and libproxy if building
--with-gnome
* libsoup/soup-proxy-resolver-gconf.c: bring this back.
* libsoup/soup-gnome-features.c
(soup_proxy_resolver_gnome_get_type): use gconf instead of
libproxy
* libsoup/Makefile.am: updates
svn path=/trunk/; revision=1247
|
|
* docs/reference/client-howto.xml: Updates: Mention
SoupSessionFeature (and link to SoupLogger, SoupCookieJar, and
SoupProxyResolverGNOME specifically). Mention forms and XML-RPC
support. Mention header-parsing methods. Give a concrete example
of connecting to SoupMessage signals. Document the (minimal)
thread-safety guarantees
* docs/reference/build-howto.xml: basic notes on pkg-config and
#include usage.
svn path=/trunk/; revision=1238
|
|
svn path=/trunk/; revision=1234
|