- Aug 25, 2016
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
... instead of relying on the pkg-config autoconf macros to be present. Fixes #972 (again...)
-
Jay Satiro authored
.. also remove same from scp
-
- Aug 23, 2016
-
-
Ales Novak authored
When we're uploading using FTP and the server issues a tiny pause between opening the connection to the client's secondary socket, the client's initial poll() times out, which leads to second poll() which does not wait for POLLIN on the secondary socket. So that poll() also has to time out, creating a long (200ms) pause. This patch adds the correct flag to the secondary socket, making the second poll() correctly wait for the connection there too. Signed-off-by: Ales Novak <alnovak@suse.cz> Closes #978
-
- Aug 22, 2016
-
-
Daniel Stenberg authored
-
- Aug 21, 2016
-
-
Daniel Stenberg authored
With commit c2f9b78a we added a new dependency on pkg-config for developers which may be unwanted. This change make the configure script still work as before if pkg-config isn't installed, it'll just use the old zlib detection logic without pkg-config. Reported-by: Marc Hörsken Fixes #972
-
Marc Hoersken authored
This reverts commit 9cb1059f. As discussed in #835 SOCKS5 supports IPv6 proxies and destinations.
-
Marco Deckel authored
Closes #820
-
Steve Holme authored
Only choose the GSSAPI authentication mechanism when the user name contains a Windows domain name or the user is a valid UPN. Fixes #718
-
Steve Holme authored
Completing commit 00417fd6 and 2708d425.
-
Steve Holme authored
From commit 2708d425.
-
- Aug 20, 2016
-
-
Marc Hoersken authored
Instead of displaying the requested hostname the one returned by the SOCKS5 proxy server is used in case of connection error. The requested hostname is displayed earlier in the connection sequence. The upper-value of the port is moved to a temporary variable and replaced with a 0-byte to make sure the hostname is 0-terminated.
-
Steve Holme authored
As of 7.25.0 and commit 54300072.
-
Marc Hoersken authored
Replace custom string formatting with Curl_printable_address. Add additional debug and error output in case of failures.
-
Marc Hoersken authored
Calling sscanf is not required since the raw IPv4 address is available and the protocol can be detected using ai_family.
-
Steve Holme authored
Made by Visual Studio's auto-correct feature and missed by me in my own code reviews!
-
Steve Holme authored
Hooked up the HTTP authentication layer to query the new 'is mechanism supported' functions when deciding what mechanism to use. As per commit 00417fd6 existing functionality is maintained for now.
-
Marc Hoersken authored
-
Marc Hoersken authored
-
Steve Holme authored
Hooked up the SASL authentication layer to query the new 'is mechanism supported' functions when deciding what mechanism to use. For now existing functionality is maintained.
-
- Aug 19, 2016
-
-
Miroslav Franc authored
-
Daniel Stenberg authored
-
- Aug 18, 2016
-
-
Steve Holme authored
As Windows SSPI authentication calls fail when a particular mechanism isn't available, introduced these functions for DIGEST, NTLM, Kerberos 5 and Negotiate to allow both HTTP and SASL authentication the opportunity to query support for a supported mechanism before selecting it. For now each function returns TRUE to maintain compatability with the existing code when called.
-
Daniel Stenberg authored
-
- Aug 17, 2016
-
-
Steve Holme authored
...and removed some old ones
-
David Woodhouse authored
RFC7512 provides a standard method to reference certificates in PKCS#11 tokens, by means of a URI starting 'pkcs11:'. We're working on fixing various applications so that whenever they would have been able to use certificates from a file, users can simply insert a PKCS#11 URI instead and expect it to work. This expectation is now a part of the Fedora packaging guidelines, for example. This doesn't work with cURL because of the way that the colon is used to separate the certificate argument from the passphrase. So instead of curl -E 'pkcs11:manufacturer=piv_II;id=%01' … I instead need to invoke cURL with the colon escaped, like this: curl -E 'pkcs11\:manufacturer=piv_II;id=%01' … This is suboptimal because we want *consistency* — the URI should be usable in place of a filename anywhere, without having strange differences for different applications. This patch therefore disables the processing in parse_cert_parameter() when the string s...
-
Daniel Stenberg authored
-
- Aug 16, 2016
-
-
Daniel Stenberg authored
This allows for better memmory debugging and torture tests.
-
Daniel Stenberg authored
This fixes tests that were added after 113f04e6 as the tests would fail otherwise. We bring back "Proxy-Connection: Keep-Alive" now unconditionally to fix regressions with old and stupid proxies, but we could possibly switch to using it only for CONNECT or only for NTLM in a future if we want to gradually reduce it. Fixes #954 Reported-by: János Fekete
-
Daniel Stenberg authored
This reverts commit 113f04e6.
-
- Aug 15, 2016
-
-
Daniel Stenberg authored
Follow-up to a96319eb (document the new behavior)
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
Follow up to a96319eb
-
Daniel Stenberg authored
-
Daniel Stenberg authored
I discovered some people have been using "https://example.com" style strings as proxy and it "works" (curl doesn't complain) because curl ignores unknown schemes and then assumes plain HTTP instead. I think this misleads users into believing curl uses HTTPS to proxies when it doesn't. Now curl rejects proxy strings using unsupported schemes instead of just ignoring and defaulting to HTTP.
-
Daniel Stenberg authored
-
- Aug 14, 2016
-
-
Marc Hoersken authored
Third commit to fix issue #944 regarding SOCKS5 error handling. Reported-by: David Kalnischkies
-
Marc Hoersken authored
Second commit to fix issue #944 regarding SOCKS5 error handling. Reported-by: David Kalnischkies
-
Marc Hoersken authored
First commit to fix issue #944 regarding SOCKS5 error handling. Reported-by: David Kalnischkies
-