* Fixed a crash when using NTLM connections [316313, probably
also 318252]. (Also 321208, which was a bug introduced in
the original fix for 316313.)
* Fixed a bug that could cause soup to suck up all available
CPU when a connection to a SoupServer was dropped by the
other side [319305, patch from Jonathan Matthew]
* Fixed the creation of struct elements in XMLRPC messages
[321362, patch from Sebastian Bauer]
* Plugged a small memory leak in SoupSocket (from Wang Xin).
* Fixed two compile problems, a gccism [320349, patch from
Roland Illig], and a strict-aliasing warning from gcc 4.1.
* Now compiles against gnutls 1.2.0 [57811]
* Fixed a bug that could result in 100% CPU usage if an SSL server closed
the connection uncleanly. [73352]
* Updated for a libgcrypt API change between 1.1.9x and 1.2.x that caused a
crash at runtime if you compiled against 1.2.x. [66342]
* SSL certificate validation failure should now always result in a status of
SOUP_STATUS_SSL_FAILED, rather than getting turned into SOUP_STATUS_IO_ERROR.
[64414]
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
Changes in libsoup from the 2.0 series (1.99.x versions) to 2.2:
* Most of the libsoup datatypes are now GObjects. (SoupUri
is currently an exception to this.)
* SoupMessage now emits signals at various stages of
processing. (Eg, "wrote_body", "got_headers".) (You
can also still use soup_message_add_*handler().)
* SoupContexts are gone; soup_message_new() now takes a URI
string.
* All formerly global state is now maintained by the
SoupSession object. (This includes the connection pool,
proxy server, cached authentication information, SSL
certificates, etc.)
* You can create a SoupSessionAsync (for 2.0-like
behavior) or SoupSessionSync (for blocking,
synchronous usage).
* You can add SoupMessageFilter objects to a session
to have certain processing automatically performed
on every message sent via that session. (Eg, setting
up handlers.)
* NTLM authentication is no longer supported by
default. You must enable it by setting the
SOUP_SESSION_USE_NTLM flag on the session.
* The preferred method of handling authentication is
now via the "authenticate" and "reauthenticate"
signals on SoupSession. (The old style, of encoding
the user and password information into the url is
also still supported.)
* The SOUP_ERROR_* values are now SOUP_STATUS_* (so that we
don't have "SOUP_ERROR_OK" and the like).
* SOUP_MESSAGE_IS_ERROR() is gone, since some cases
want to include 3xx responses and some don't.
* SOUP_ERROR_CANT_AUTHENTICATE and
SOUP_ERROR_CANT_AUTHENTICATE_PROXY are now gone,
since they didn't carry any information that
SOUP_STATUS_UNAUTHORIZED and
SOUP_STATUS_PROXY_UNAUTHORIZED don't.
* DNS errors now show up as the new status code
SOUP_STATUS_CANT_RESOLVE rather than being mixed in
with SOUP_ERROR_CANT_CONNECT.
* Minimal SOAP support has been added back, via
SoupSoapMessage/SoupSoapResponse
* The HTTP I/O state machine was completely rewritten, fixing
numerous crashes, leaks, and protocol errors.
* SoupUri now conforms to RFC 2396. Mostly.
* Various test programs have been added under tests/
* Removed:
* Support for OpenSSL (which was horribly buggy) and
Mozilla NSS (which was never finished). We only
support GNUTLS for SSL now.
* SOCKS support
* CGI support in SoupServer
needed by evolution-data-server
Libsoup is an HTTP library implementation in C. It was originally part
of a SOAP (Simple Object Access Protocol) implementation called Soup, but
the SOAP and non-SOAP parts have now been split into separate packages.
libsoup uses the Glib main loop and is designed to work well with GTK
applications. This enables GNOME applications to access HTTP servers
on the network in a completely asynchronous fashion, very similar to
the Gtk+ programming model (a synchronous operation mode is also
supported for those who want it).
Features:
* Completely Asynchronous
* Connection cache
* HTTP chunked transfer support
* HTTP, SOCKS4, and SOCKS5 authenticated proxy support
* SSL Support using OpenSSL or GnuTLS
* Client support for Digest, NTLM, and Basic authentication
* HTTP server
* Server support for Digest and Basic authentication
