| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
| |
Add :http-aliases and :https-aliases properties to SoupServer, to
allow it to handle requests like:
GET daap://host:port/path HTTP/1.1
https://bugzilla.gnome.org/show_bug.cgi?id=703694
|
| |
|
| |
|
|
|
|
|
|
| |
If doing a read_line()/read_until() in a subclass, we need to use the
subclass's read implementation rather than just going directly to the
base stream.
|
|
|
|
|
|
|
|
| |
When closing a chunked stream, we need to write the final 0-length
chunk. However, we can only do that if we successfully wrote the
previous chunk.
https://bugzilla.gnome.org/show_bug.cgi?id=703297
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=691840
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=706338
|
|
|
|
|
|
|
| |
The refcounting test had a race condition. Fix it by just waiting for
the stream to be destroyed, rather than asserting it already has been.
https://bugzilla.gnome.org/show_bug.cgi?id=698305
|
| |
|
|
|
|
|
|
|
| |
Don't include the scope ID in the "Host" header.
Make SoupURI correctly parse both correct and incorrect scope IDs, and
add checks for that in tests/uri-parsing.
|
|
|
|
|
|
|
|
|
|
|
| |
SoupAddress's GSocketAddressEnumerator implementation was passing the
wrong GMainContext to soup_address_resolve_async(), although it only
ended up affecting the address-is-already-resolved case. Fix this.
Also, remove the async_lookups list from SoupAddressPrivate, and just
make multiple calls to the resolver if there are multiple calls to
soup_address_resolve_async() at once, since that code didn't handle
different GMainContexts correctly.
|
|
|
|
|
|
|
| |
Use GNetworkAddress to try to parse IPv6 addresses with scope IDs,
rather than just letting the scope ID get dropped.
Part of https://bugzilla.gnome.org/show_bug.cgi?id=669724
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
soup_message_headers_get_ranges() doesn't check satisfiability (and
can't without changing its API) so add a new
soup_message_headers_get_ranges_internal(), and use that from
soup-message-server-io so we can handle this properly. Test that it
works from range-test.
Pointed out on the mailing list by Kai Lüke.
|
| |
|
|
|
|
|
|
|
|
| |
It was never meant to work, and can lead to weird behaviour and crashes.
Also mention this more explicitly in the documentation for
soup_session_[un]pause_message().
Helps: https://bugzilla.gnome.org/show_bug.cgi?id=703461
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
SoupLogger won't print any information upon
response until the "got-body" or
"got-informational" signals are received. If the
response message has been cancelled or requeued
first, we miss the headers information, even when
we would have been already able to print it.
Now, upon response, if the logging has not yet
happened when the "finished" signal is triggered,
we do perform the logging then.
https://bugzilla.gnome.org/show_bug.cgi?id=703200
|
|
|
|
|
|
|
| |
The URI grammar allows a scheme to have digits in it after the first
character, and doesn't allow [.+-] in the first character.
https://bugzilla.gnome.org/show_bug.cgi?id=703776
|
|
|
|
|
|
|
|
| |
This fixes an issue where the build would fail with a UnicodeDecodeError
when run in a non-utf8 locale (which is typical in build environments)
using Python 3.
https://bugzilla.gnome.org/show_bug.cgi?id=702534
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Finish up the GProxyResolver porting started in 2.42 by removing all
the non-GProxyResolver proxy code from SoupSocket and SoupConnection
and implementing SoupSession:proxy-uri in terms of
GSimpleProxyResolver. If the user adds a SoupProxyResolverDefault to
the session, just use its GProxyResolver directly instead. If the user
adds any other kind of SoupProxyURIResolver to the session, use the
new SoupProxyResolverWrapper, which is a GProxyResolver that
translates from SoupProxyURIResolver.
https://bugzilla.gnome.org/show_bug.cgi?id=680273
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Rename SoupKnownStatusCode to SoupStatus (so that the type name
matches the enum values), and then, for backward-compatibility, add a
new SoupKnownStatusCode enum with equivalent values so that
introspection-using code that was doing "SoupKnownStatusCode.OK", etc,
will still work.
https://bugzilla.gnome.org/show_bug.cgi?id=684409
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=637039
|
|
|
|
|
| |
(Primarily to move automake 1.13's test-driver out of the top level so
that the tests/ subdir autocompletes correctly again.)
|
|
|
|
| |
to make automake 1.13 happy
|
| |
|
|
|
|
|
|
|
|
|
| |
get_connection() assumed that REMOTE_DISCONNECTED connections would get
implicitly cleaned up elsewhere in the code, which is true for async
sessions, but not sync ones. This could lead to connection exhaustion and
hence hangs.
Closes: https://bugzilla.gnome.org/show_bug.cgi?id=703463
|
|
|
|
| |
Closes: https://bugzilla.gnome.org/show_bug.cgi?id=703461
|
|
|
|
|
|
|
|
|
|
| |
The "get" example is now able to handle a new "-o"
parameter specifying the path of a file in which
to write the received body of a "GET" operation.
If the file exists, it will be overwritten.
https://bugzilla.gnome.org/show_bug.cgi?id=703229
|
|
|
|
|
|
|
|
| |
Now, instead of printing the debug information
manually we use SoupLogger for this with the "-d"
flag.
https://bugzilla.gnome.org/show_bug.cgi?id=703231
|
| |
|
|
|
|
|
|
|
|
| |
This is necessary to allow passing the query on to another thread, given
that the developer adds another reference. With the current destroy
thing this will not work.
https://bugzilla.gnome.org/show_bug.cgi?id=702793
|
| |
|
|
|
|
|
|
|
| |
g_cclosure_marshal_generic() is the default signal handler starting
from glib 2.29.12. libsoup already requires glib 2.33.1.
https://bugzilla.gnome.org/show_bug.cgi?id=686042
|
|
|
|
|
|
|
| |
Add a test for the leak in bug 700472, which also turned up another
leak.
https://bugzilla.gnome.org/show_bug.cgi?id=700472
|
|
|
|
|
|
|
|
|
| |
soup_session_kick_queue() should have been locking conn_mutex around
signalling conn_cond, since otherwise there's a race condition where
it could signal just before someone else starts waiting. (In reality,
this is unlikely to cause problems, since we tend to signal conn_cond
more than is actually necessary. But maybe we'll get better about not
doing that in the future.)
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=700472
|
|
|
|
|
|
|
| |
Make SoupSession handle GDummyTlsBackend a little better (and add
a test for it).
https://bugzilla.gnome.org/show_bug.cgi?id=700518
|
|
|
|
|
|
|
|
|
| |
When sending a CONNECT request, don't include auth headers intended
for the origin server. (And in particular, when doing NTLM through a
proxy, don't assume that the NTLM auth succeeded because the proxy
returned 200 to the CONNECT request.)
Part of https://bugzilla.gnome.org/show_bug.cgi?id=698728
|
| |
|
|
|
|
|
|
| |
Resolves implicit declaration failures of functions like 'strchr'
https://bugzilla.gnome.org/show_bug.cgi?id=700003
|
| |
|
|
|
|
|
|
|
|
|
| |
If a SOURCES variable changes, we need to recheck the generated files,
since a file may have been removed from SOURCES, but still be
referenced in a previously-generated -enum-types.c file, etc. So make
these generated files depend on Makefile.
Also, update spacing of silent rules to match current automake.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
soup-portability.h created portability problems (ha!) because the
windows headers do "#define interface struct", conflicting with
variable names elsewhere.
The only thing that needed soup-portability.h in the public headers
was soup-address.h, which uses struct sockaddr. But we can just do a
forward declaration of that type rather than actually pulling in the
headers. Then soup-address.h can stop including soup-portability.h,
and we can use gio/gnetworking.h in the handful of other places that
need networking-related includes.
This may possibly break some other modules that depended on implicitly
getting network includes as a side effect of including soup.h...
https://bugzilla.gnome.org/show_bug.cgi?id=692134
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=698220
|
|
|
|
|
|
|
|
|
| |
When creating a GProxyAddressEnumerator, the destination URI passed to
it must include the port number, or the proxy may end up trying to
connect to port 0. libsoup was omitting the port number when it was
the default for the protocol.
https://bugzilla.gnome.org/show_bug.cgi?id=698163
|