- 15 Jun, 2015 7 commits
-
-
Viktor Szakats authored
* use SSL/TLS where available * follow permanent redirects
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
"At condition p_request, the value of p_request cannot be NULL." Coverity CID 1306668.
-
Daniel Stenberg authored
... by removing the "do {} while (0)" block. Coverity CID 1306669
-
Daniel Stenberg authored
-
Daniel Stenberg authored
use \fI-style instead of .BR for references
-
- 14 Jun, 2015 5 commits
-
-
Daniel Stenberg authored
... to simplify checking when PUT _or_ POST have completed. Reported-by: Frank Meier Bug: http://curl.haxx.se/mail/lib-2015-06/0019.html
-
Dan Fandrich authored
-
Drake Arconis authored
-
Drake Arconis authored
-
Jay Satiro authored
-
- 13 Jun, 2015 1 commit
-
-
Daniel Stenberg authored
-
- 11 Jun, 2015 3 commits
-
-
Daniel Stenberg authored
-
Joel Depooter authored
Some servers will request a client certificate, but not require one. This change allows libcurl to connect to such servers when using schannel as its ssl/tls backend. When a server requests a client certificate, libcurl will now continue the handshake without one, rather than terminating the handshake. The server can then decide if that is acceptable or not. Prior to this change, libcurl would terminate the handshake, reporting a SEC_I_INCOMPLETE_CREDENTIALS error.
-
Daniel Stenberg authored
-
- 10 Jun, 2015 1 commit
-
-
Daniel Stenberg authored
-
- 09 Jun, 2015 5 commits
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
and a conversion to markdown. Removed the lib/README.* files. The idea being to move toward having INTERNALS as the one and only "book" of internals documentation. Added a TOC to top of the document.
-
Jay Satiro authored
Although OpenSSL 1.1.0+ deprecated SSLv23_client_method in favor of TLS_client_method LibreSSL and BoringSSL didn't and still use SSLv23_client_method. Bug: https://github.com/bagder/curl/commit/49a6642#commitcomment-11578009 Reported-by: <asavah@users.noreply.github.com>
-
- 08 Jun, 2015 7 commits
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
When CURL_SOCKET_BAD is returned in the callback, it should be treated as an error (CURLE_COULDNT_CONNECT) if no other socket is subsequently created when trying to connect to a server. Bug: http://curl.haxx.se/mail/lib-2015-06/0047.html
-
Daniel Stenberg authored
-
Ville Skyttä authored
-
Ville Skyttä authored
-
Linus Nielsen authored
-
Jay Satiro authored
- Try building a chain using issuers in the trusted store first to avoid problems with server-sent legacy intermediates. Prior to this change server-sent legacy intermediates with missing legacy issuers would cause verification to fail even if the client's CA bundle contained a valid replacement for the intermediate and an alternate chain could be constructed that would verify successfully. https://rt.openssl.org/Ticket/Display.html?id=3621&user=guest&pass=guest
-
- 05 Jun, 2015 3 commits
-
-
Daniel Stenberg authored
Stop linking to the curl.haxx.se anchor pages, they are usually only themselves pointers to the real page so better point there directly instead.
-
Daniel Stenberg authored
-
Daniel Stenberg authored
The protocol is named "HTTP/2" after all. It is an alias for the existing CURL_HTTP_VERSION_2_0 enum.
-
- 04 Jun, 2015 6 commits
-
-
Daniel Stenberg authored
ERR_error_string_n() was introduced in 0.9.6, no need to #ifdef anymore
-
Daniel Stenberg authored
Code for OpenSSL 0.9.4 serves no purpose anymore!
-
Daniel Stenberg authored
It was present for OpenSSL 0.9.5 code but we only support 0.9.7 or later.
-
Daniel Stenberg authored
The existing callback served no purpose.
-
Daniel Stenberg authored
-
Jay Satiro authored
Prior to this change any-domain cookies (cookies without a domain that are sent to any domain) were exported with domain name "unknown". Bug: https://github.com/bagder/curl/issues/292
-
- 03 Jun, 2015 1 commit
-
-
Daniel Stenberg authored
-
- 02 Jun, 2015 1 commit
-
-
Jay Satiro authored
Bug: https://github.com/bagder/curl/pull/258#issuecomment-107915198 Reported-by: Gisle Vanem
-