Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Address the possibility of data: URLs containing null characters when the data
request is being performed. The uri_decoded_copy method is enhanced with a
third argument, a pointer to an integer that should be set to the length of
decoded data when provided. This length is then set as the request's content
length.
A test checking the correct behavior is added in requester-test. Calls to
uri_decoded_copy where the length of the decoded output is not required are
adjusted to provide NULL as the third argument.
|
|
|
|
|
|
|
|
|
|
Now that GSocketClient lets you override its proxy resolver, allow
setting a GProxyResolver on a SoupSession, to eventually pass on to
the GSocketClient.
(In the interest of not breaking things this late in the release
cycle, all of the old SoupProxyURIResolver code still exists as well,
in parallel, but in 2.43 it will be removed and replaced with
GProxyResolver-based backward-compat stuff.)
https://bugzilla.gnome.org/show_bug.cgi?id=680273
|
|
|
|
|
|
Normally when sending a 401 response, a server re-sends the initial
WWW-Authenticate challenge. However, it doesn't actually have to, and
libsoup was getting confused if it didn't. Fix that.
https://bugzilla.redhat.com/show_bug.cgi?id=916224
|
|
Every year or two some bug comes up that makes libsoup retry a request
infinitely. (Also, apps can do this on their own by not paying
attention to the "retrying" flag in SoupSession::authenticate.) Move
the "too many redirects" code and rework it to handle all possible
cases of "message gets resent a suspicious number of times".
|
|
|
|
SoupCache was not updating the cached headers on conditional requests. We
were only doing it for revalidations started by libsoup clients.
This also properly reset the values of freshness_lifetime and
must_revalidate on revalidations. These two fields were keeping their
original values even if the server wasn't providing such information.
Finally this adds a new cache test (do_header_test) and fixes the one
disabled with #ifdefs (second revalidations).
https://bugzilla.gnome.org/show_bug.cgi?id=695121
|
|
The variable GLIB_COMPILE_RESOURCES is already set by AM_PATH_GLIB_2_0
macro. Spotted by Csaba Osztrogonác.
https://bugzilla.gnome.org/show_bug.cgi?id=694942
|
|
This will ensure that the GMainContext is not freed at least until we get
rid of the queue item. This was causing crashes when synchronously
retrieving resources in WebKit as it uses a different GMainContext for each
of those synchronous requests.
https://bugzilla.gnome.org/show_bug.cgi?id=694920
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
get, simple-httpd, and simple-proxy are more example code than test
programs, so move them into a separate directory.
Also, remove "dns", which was once a sort-of test of SoupAddress, but
is now just a redundant sort-of test of GResolver.
|
|
Remove accumulated cruft, mostly from things we used to depend on but
don't any more.
Also a few minor drive-by configure cleanups
|
|
Signed-off-by: Gheyret Kenji <gheyret@gmail.com>
|
|
|
|
|
|
automake interprets exit code 77 as meaning "skipped", so have the
various apache-dependent, php-dependent, and curl-dependent tests do
that, and compile them unconditionally. (Although, to avoid "unused"
warnings, we end up #ifdeffing out the whole file.)
|
|
Specifying serial-tests in AM_INIT_AUTOMAKE breaks the build with
automake 1.11, so the only way to support both 1.11 and 1.13 is to
make the tests work under the parallel harness. Fortunately this
wasn't that hard.
|
|
|
|
The parallel test harness (which is the default as of automake 1.13)
doesn't let you use make functions in the definition of TESTS. (It
generates an invalid Makefile in this case.) Since the tests as
currently written won't work with the parallel harness anyway (since
each apache-based test stops apache when it's done), just force the
serial harness for now.
https://bugzilla.gnome.org/show_bug.cgi?id=694135
|
|
The SoupCache does not get any information from sniffed content types as it
works at a lower level. That's why sometimes we might not have any
Content-Type information for a cached resource (if the server does not
specify it).
|
|
|
|
|
|
|
|
|
|
|
|
Added do_refcounting_test that checks that streams do not leak any
reference when a message is cancelled just before starting to read.
This test also need a new cancel flag called
SOUP_TEST_REQUEST_CANCEL_AFTER_SEND_FINISH.
https://bugzilla.gnome.org/show_bug.cgi?id=682527
|