summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix soup_session_get_async_result_message() with ↵Patrick Griffis2021-03-121-0/+5
| | | | soup_session_send_and_read_async()
* docs: Remove outdated logging notePatrick Griffis2021-03-111-4/+0
|
* 2.99.22.99.2Patrick Griffis2021-03-102-1/+17
|
* Require body streams implement GPollableInputStreamPatrick Griffis2021-03-091-2/+3
|
* logger: re-add support for logging request/response bodiesDaniel Kolesa2021-03-0912-33/+751
|
* Implement skip for SoupClientInputStream and SoupFilterInputStreamDaniel Kolesa2021-03-083-18/+50
| | | | | | | | | this enables calling `g_input_stream_skip` on response body input streams and getting predictable behavior (i.e. read but without explicit storage) the `skip` implementation for body input stream was insufficient, resulting in the stream state never incrementing properly
* Remove 2.99 version macrosPatrick Griffis2021-03-053-7/+6
| | | | The first API will be 3.0
* Use g_memory_output_stream_new_resizable()Patrick Griffis2021-03-052-5/+5
|
* Fix compile warningsPatrick Griffis2021-03-054-4/+5
|
* build: Build with more warningsPatrick Griffis2021-03-051-2/+8
|
* Add a method to override the remote connection.Robert Ancell2021-03-0511-10/+347
| | | | | | This allows using a Unix socket to communicate on. Fixes https://gitlab.gnome.org/GNOME/libsoup/-/issues/75
* Replace remote-uri with remote-connectable in SoupConnectionRobert Ancell2021-03-052-44/+24
|
* Add new api to preconnect to a given uriCarlos Garcia Campos2021-03-056-25/+574
| | | | | | A new connection is started that can be reused by a future request for the same host. This is needed by WebKit to implement link preconnect https://w3c.github.io/resource-hints/#preconnect
* session: remove the basic APIsCarlos Garcia Campos2021-03-047-752/+36
| | | | | | | Now that we have soup_session_send_and_read() the only difference is that we need to build a SoupMessage first. Fixes #216
* examples: use soup_session_send in get exampleCarlos Garcia Campos2021-03-041-5/+10
| | | | | Instead of the basic API that will be removed soon. Also bring back the head command line option now that we create the message again.
* session: add soup_session_get_async_result_messagecarlosgc/async-result-messageCarlos Garcia Campos2021-03-046-7/+43
| | | | | This is useful to get the SoupMessage of an async operation from the ready callback.
* session: add soup_session_send_and_read APIscarlosgc/send_and_readCarlos Garcia Campos2021-03-0315-100/+228
| | | | | | This is convenient API to send a message and read its body into a GBytes. This should replace the basic APIs since it covers the same use case, but using a SoupMessage instead of a URI and with ore flexibility.
* vala: Drop deprecated custom bindingsRico Tzschichholz2021-02-271-4/+0
|
* session: fix the queue order for items with same priorityCarlos Garcia Campos2021-02-272-1/+81
| | | | For items with the same priority we still want to append
* Remove SoupMessageQueuecarlosgc/session-queueCarlos Garcia Campos2021-02-2610-439/+203
| | | | | We can just use a GQueue instead now that we don't try to support multiple threads
* session: remove async-context propertyCarlos Garcia Campos2021-02-2511-340/+102
| | | | | Stop supporting multiple contexts, the session is expected to be used always in the thread from which it was created.
* ssl-test: do not fail if we get connection closed instead of certificate ↵Carlos Garcia Campos2021-02-251-1/+5
| | | | | | required It's a glib-networking bug that is making this test flaky
* Fix some functions that weren't changed from a boolean to an enum.Robert Ancell2021-02-256-6/+6
| | | | This function was changed in 96b890dc8
* timeout-test: port the new API and unskip itCarlos Garcia Campos2021-02-241-40/+34
|
* cache-test: fix session extra reference on endCarlos Garcia Campos2021-02-241-4/+2
| | | | Just iterate the main loop to ensure the message finishes.
* Update Galician translationFran Dieguez2021-02-241-3/+2
|
* 2.99.12.99.1Patrick Griffis2021-02-236-12/+17
|
* session: add public getters and setters for the SoupSession propertiesCarlos Garcia Campos2021-02-238-142/+605
| | | | | Also make max-conns and max-conns-per-host construct only and ensure all setters emit the GObject::notify signal when the value changes.
* test: simplify /ssl/tls-interaction test by using SoupServerCarlos Garcia Campos2021-02-233-93/+50
| | | | The test is still flaky, but due to a glib-networking bug.
* server: rename SoupSocket:ssl-creds as SoupSocket::tls-certificateCarlos Garcia Campos2021-02-232-28/+21
| | | | It's always a GTlsCertificate in the server side.
* server: remove unused property SoupSocket:is-serverCarlos Garcia Campos2021-02-233-102/+1
| | | | SoupSocket is only used on the server side now.
* Updated Danish translationAsk Hjorth Larsen2021-02-231-194/+202
|
* docs: Remove incorrect redirect docsPatrick Griffis2021-02-222-39/+0
| | | | These changes never happened.
* Fix reference to SOUP_VERSION_2_24Patrick Griffis2021-02-221-2/+2
| | | | It isn't defined.
* Update Indonesian translationKukuh Syafaat2021-02-211-105/+119
|
* Extend test cert to 2049Bernhard M. Wiedemann2021-02-191-8/+8
| | | | | | | | | | | | | | | | | | used certtool -u \ --load-ca-privkey ./tests/test-key.pem \ --load-ca-certificate ./tests/test-cert.pem \ --load-certificate ./tests/test-cert.pem Without this patch, 3 tests failed in 2027 11/29 misc-test FAIL 0.67s (exit status 1) 21/29 server-test FAIL 0.12s (exit status 1) 25/29 timeout-test FAIL 4.08s (killed by signal 5 SIGTRAP) Background: As part of my work on reproducible builds for openSUSE, I check that software still gives identical build results in the future. The usual offset is +15 years, because that is how long I expect some software will be used in some places. This showed up failing tests in our package build. See https://reproducible-builds.org/ for why this matters.
* session: Remove ssl-use-system-ca-file propertyCarlos Garcia Campos2021-02-196-146/+99
| | | | | | SoupSession:tls-database is enough. When not set the default will be used. Also ensure that we don't get the default tls database and proxy resolver unless the property getters are called.
* Update British English translationZander Brown2021-02-181-108/+125
|
* content-sniffer: empty resources should be considered text/plaincarlosgc/sniff-emptyCarlos Garcia Campos2021-02-172-5/+10
| | | | Instead of application/octet-stream according to the HTML5 spec
* server: remove unused property definitionsCarlos Garcia Campos2021-02-171-2/+0
|
* Update Hungarian translationBalázs Meskó2021-02-141-107/+123
|
* message: do not use underscore in signal namesCarlos Garcia Campos2021-02-111-7/+7
|
* docs: use Returns instead of Return value in documentationCarlos Garcia Campos2021-02-1132-156/+156
|
* docs: remove since tags from documentationCarlos Garcia Campos2021-02-1137-282/+2
|
* Remove http and https aliases supportCarlos Garcia Campos2021-02-1115-471/+37
| | | | | It doesn't seem to be used. If needed we can just bring it back in the future.
* logger: Fix memory leakCarlos Garcia Campos2021-02-111-1/+4
|
* hsts: Move hsts-enforced signal from SoupHSTSEnforcer to SoupMessageCarlos Garcia Campos2021-02-116-91/+119
| | | | For convenience and also consistency with other features.
* WebSockets: do not report connection errors as handshake failurescarlosgc/websocket-connection-errorCarlos Garcia Campos2021-02-102-3/+41
| | | | | | | | | | We are assuming that when not switching protocols after a request is because the server didn't accept the handshake, but we can fail even earlier if there's a connection error. In libsoup 2 we could check if it was a connection error by checking the message status was SOUP_STATUS_CANT_CONNECT or SOUP_STATUS_CANT_CONNECT_PROXY. Now that we no longer use the message status for transport errors, we should make soup_session_websocket_connect_async() fail with the connection error.
* build: Print summary of configurationPatrick Griffis2021-02-081-1/+31
|
* Update Turkish translationEmin Tufan Çetin2021-02-071-109/+122
|
View Lorry Controller Status