summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix reserved opcodeItalo Guerrieri2018-01-101-2/+4
| | | | | | | | | Some opcode are reserved for future implementations of the WebSocket protocol. If these reserved code are send, the connection needs to be closed. Fix Autobahn test cases 4.*. https://bugzilla.gnome.org/show_bug.cgi?id=792113
* Fix reserved bitItalo Guerrieri2018-01-101-0/+5
| | | | | | | | | Close connection if reserved bits are different than zero. These bits should always be 000 because libsoup does not support extentions that need to use these reserved bits. Fix Autobahn test cases 3.* https://bugzilla.gnome.org/show_bug.cgi?id=792113
* Fix big control message payloadItalo Guerrieri2018-01-101-3/+6
| | | | | | | | Close connection with protocol error if the payload of a control message is bigger than 125 octets. Fix Authobahn test case 2.5. https://bugzilla.gnome.org/show_bug.cgi?id=792113
* soup-headers: accept any 3 digit number as message status codeCarlos Garcia Campos2018-01-093-4/+12
| | | | | | | | | | | | The HTTP RFC says that status code is extensible, but the category must be known by the client. However, popular websites like linkedin use invalid status codes such as 999, and all the major browsers handle that correctly. There are also WPT tests checking status codes greater than 599 in XMLHTTPRequests. So, let's parse the status code, only failing if it's not a 3 digit number and letting the user handle any other particular case. https://bugzilla.gnome.org/show_bug.cgi?id=792124
* 2.61.22.61.2Claudio Saavedra2018-01-082-1/+6
|
* session: don't request Keep-Alive for upgraded connectionsLionel Landwerlin2018-01-041-1/+3
| | | | | | | | | | | When an upgrade is requested through "Connection: Upgrade" (used for setting up websocket connection for example), there is no need to request Keep-Alive. It turns out doing both is confusing some servers based on the h2o library. https://bugzilla.gnome.org/show_bug.cgi?id=788723
* 2.61.12.61.1Claudio Saavedra2017-12-112-2/+15
|
* gobject: explicitly cast on g_object_ref/unref() callsClaudio Saavedra2017-12-112-2/+2
| | | | | GObject now issues warnings for implicit casts on these being called. See https://bugzilla.gnome.org/show_bug.cgi?id=790697.
* SoupCache: fix the timestamp for responsesClaudio Saavedra2017-11-301-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=791031
* Don't use C++ comments as libsoup uses C89Tomas Popela2017-11-162-3/+3
|
* Fix bug URI for non gnome.org bugs in unit testsTomas Popela2017-11-152-2/+4
|
* Fix possibly uninitialized value in ssl-testTomas Popela2017-11-151-1/+1
| | | | | | ssl-test.c: In function ‘main’: ssl-test.c:465:3: warning: ‘server’ may be used uninitialized in this function [-Wmaybe-uninitialized] soup_test_server_quit_unref (server);
* heap-buffer-overflow in soup_ntlm_parse_challenge()Milan Crha2017-11-141-0/+5
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=788037
* tld-parser: use Python 3Ross Burton2017-10-301-1/+1
| | | | | | | The world is moving to Python 3 so do our bit by using Python 3 to run the TLD parser. https://bugzilla.gnome.org/show_bug.cgi?id=785735
* 2.60.22.60.2Claudio Saavedra2017-10-272-1/+16
|
* Visual Studio builds: Enhance security of x64 binariesChun-wei Fan2017-10-201-0/+4
| | | | | | | Use the HIGHENTROPYVA linker option on x64 builds with MSVC 2012 and later to enhance the security of the built binaries. Pointed out by Ignacio Casal Quinteiro.
* Bug 789099 - Warnings while generating introspection filesTomas Popela2017-10-192-12/+10
| | | | Reorganize the documentation to fix the warnings.
* Bug 789096 - format-zero-length warning triggered in soup-logger.cTomas Popela2017-10-181-8/+8
| | | | | The calls are supposed to print a new line - fix them. Also fix a white space errors while touching the file.
* Update Nepali translationPawan Chitrakar2017-10-161-4/+4
|
* soup: some typos in websocket API docNirbheek Chauhan2017-10-131-3/+3
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=788920
* 2.60.12.60.1Claudio Saavedra2017-10-112-1/+14
|
* [l10n] Updated Catalan (Valencian) translationXavi Ivars2017-10-051-41/+92
|
* SoupCache: fix setting default value for cache dirCosimo Cecchi2017-10-031-23/+14
| | | | | | | | | | | | The documentation mentions that a value of NULL can be used to let SoupCache use its default, but code currently tries to call g_file_test() on NULL in that case, which will cause a critical warning to be generated. Refactor how the cache dir default value is initialized to avoid that issue. https://bugzilla.gnome.org/show_bug.cgi?id=788452
* Unbalanced G_GNUC_BEGIN_IGNORE_DEPRECATIONS use in soup-session.cZan Dobersek2017-10-021-1/+1
| | | | | | | | The G_GNUC_BEGIN_IGNORE_DEPRECATIONS macro, as used in soup_session_remove_feature_by_type(), should be balanced by the complementary G_GNUC_END_IGNORE_DEPRECATIONS macro. https://bugzilla.gnome.org/show_bug.cgi?id=787166
* Bug 788238 - Fallback to another authentication type if the current failedTomas Popela2017-09-271-6/+6
| | | | | | | | Fallback to another authentication type if the current failed. More specifically if the Negotiate failed (kerberos is not properly configured), then libsoup should fallback to Basic auth (if server supports it). Currently in such case it is not possible to load the page at all (in WebKitGTK+).
* 2.60.02.60.0Dan Winship2017-09-122-4/+7
|
* Updated Dutch translation Master 3.26hanniedu2017-09-121-33/+101
|
* Fixes to Catalan translationJordi Mas2017-09-101-3/+4
|
* Updated Danish translationAsk Hjorth Larsen2017-08-281-24/+25
|
* Update Catalan translationJordi Mas2017-08-221-35/+36
|
* Add Nepali translationPawan Chitrakar2017-08-202-0/+176
|
* 2.59.90.12.59.90.1Dan Winship2017-08-102-1/+8
|
* Fix chunked decoding buffer overrun (CVE-2017-2885)Dan Winship2017-08-101-11/+11
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=785774
* 2.59.902.59.90Dan Winship2017-08-072-2/+58
|
* Always use "wss" as an alias for "https"Nirbheek Chauhan2017-08-076-11/+27
| | | | | | | | Also fix a bunch of places that were comparing uri->scheme directly with SOUP_URI_SCHEME_HTTPS instead of using the private function soup_uri_is_https(). https://bugzilla.gnome.org/show_bug.cgi?id=784786
* Fix string typoIsaac Jurado2017-08-071-2/+2
| | | | Found by lintian.
* Bug 785660 - add payload to Ping framesDavid Woodhouse2017-08-071-1/+4
| | | | | Some servers seem to close the connection if we send a Ping frame without any payload. Send a static "libsoup" as payload each time.
* Bug 785660 - emit "pong" signal when Pong frame receivedDavid Woodhouse2017-08-072-1/+48
| | | | This allows applications to detect a stalled connection.
* soup-message-io: Do not fail when there's no empty line after headersCarlos Garcia Campos2017-08-071-13/+8
| | | | | | | | | | | The spec says there should be an empty line (\r\n) between the response headers and the body. However, some servers don't include the empty line when the response doesn't have a body. This is causing several WebKit tests to fail, because some of the imported w3c tests do not include that empty line. Those tests pass in firefox, chromium and safari, so at least those other browsers allow that. https://bugzilla.gnome.org/show_bug.cgi?id=780352
* Fix out-of-bounds read in URI parsingDan Winship2017-08-072-2/+6
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=785042
* websocket-connection: avoid printing debug message when there is no errorIgnacio Casal Quinteiro2017-07-171-2/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=784935
* tests: Update test-cert.pemJan Alexander Steffens (heftig)2017-07-141-15/+16
| | | | | | | | | | This patch is copied from gst-plugins-good, where souphttpsrc tests recently started failing because GnuTLS no longer accepts the certificate: https://bugzilla.gnome.org/show_bug.cgi?id=784005 The new certificate features SAN and SHA256 and is accepted by GnuTLS. https://bugzilla.gnome.org/show_bug.cgi?id=784949
* Only set "ssl-ca-file" in examples/get if provided on the commandlineSebastian Dröge2017-07-041-1/+2
| | | | | | | Otherwise the default system CA database is not going to be used if nothing is given on the commandline, and certificate verification fails. https://bugzilla.gnome.org/show_bug.cgi?id=784259
* Fix sniffing of un-Content-Typed XMLDan Winship2017-07-034-1/+17
| | | | https://bugs.webkit.org/show_bug.cgi?id=173923
* Authentication should success in some cases when gss_init_sec_context() ↵Tomas Popela2017-06-221-4/+19
| | | | | | | | | | | | | | returns error Unfortunately, so many programs (curl, Firefox) ignore the return token that is included in the response, so it is possible that there are servers that send back broken stuff. Try to behave in the right way (pass the token to gss_init_sec_context()), show a warning, but don't fail if the server returned 200. There is an internal Red Hat site that triggers the described situation and the "Invalid token was supplied: Unknown error" is being printed to the console.
* Can't access sites that request closing the connection during 401Tomas Popela2017-06-221-2/+27
| | | | | | | | | | | | | | | When a 401 message is received, a new token is generated and saved in the SoupNegotiateConnectionState's respose header. Later when the connection is closed (as requested by the server), the state is destroyed together with the response header. When a new request is being created and we are asked for the connection authorization, the newly created connection state doesn't have it set. At this point if the connection state is newly created, generate a new token together with the response header that will be returned as the connection authorization. Also modify how the warning from the soup_gss_build_response is printed to differentiate if there was a failure during soup_gss_client_init or soup_gss_client_step.
* Rework some of the SoupAuthNegotiate internalsTomas Popela2017-06-223-46/+43
| | | | | | | | | | | | | | | | | | | | There are several problems with the current state. The main problem is that the SoupMessage can outlive the SoupAuthNegotiate object and if the SoupMessage signals handlers are active then they could be called with invalid SoupAuthNegotiate object. To avoid that use the g_signal_connect_data() and increase the reference on the SoupAuthNegotiate object. Also rework how we are connecting the 'got_headers' signal handler to the SoupMessage object, so they are really connected only once, even if the GSS mechanism involves multiple rounds. The whole concept of how we are working with the SoupAuthNegotiateConnectionState is also wrong. When the connection state is created it's saved to the private structure and then accessed from there. The problem is that another state for different message could be created in the mean time and that one would overwrite the currently set (or if one would be freed then it would erase the one that is currently set). To solve this expose the SoupConnectionAuth's get_connection_state_for_message() and call it when we need the connection state object.
* Don't leak the SoupMessage and SoupSession objects in the examples/get utilityTomas Popela2017-06-221-0/+3
|
* Updated Esperanto translationKristjan SCHMIDT2017-06-111-34/+140
|
* win32/replace.py: Fix replacing items in files with UTF-8 contentChun-wei Fan2017-05-091-2/+8
| | | | | | | | | Some files that this script will process might have UTF-8 items in there, which can cause problems on Python 3.x as it is more strict and careful on unicode issues. Fix this by: -Doing what we did before on Python 2.x -Opening the file with encoding='utf-8' on Python 3.x
View Lorry Controller Status