- Oct 29, 2014
-
-
Daniel Stenberg authored
... and allow building with nghttp2 but completely without NPN and ALPN, as nghttp2 can still be used for plain-text HTTP. Reported-by: Lucas Pardue
-
Daniel Stenberg authored
... since the conditional in the code are now based on OpenSSL versions instead to better support non-configure builds.
-
Daniel Stenberg authored
-
Steve Holme authored
-
Steve Holme authored
conversion from 'size_t' to 'unsigned int', possible loss of data
-
Steve Holme authored
Return a more appropriate error, rather than CURLE_OUT_OF_MEMORY when acquiring the credentials handle fails. This is then consistent with the code prior to commit f7e24683 when log-in credentials were empty.
-
Steve Holme authored
Fixed the ability to use the current log-in credentials with DIGEST-MD5. I had previously disabled this functionality in commit 607883f1 as I couldn't get this to work under Windows 8, however, from testing HTTP Digest authentication through Windows SSPI and then further testing of this code I have found it works in Windows 7. Some further investigation is required to see what the differences are between Windows 7 and 8, but for now enable this functionality as the code will return an error when AcquireCredentialsHandle() fails.
-
Kamil Dudka authored
Its last use has been removed by the previous commit.
-
Kamil Dudka authored
This code was already deactivated by commit ec783dc1.
-
Kamil Dudka authored
-
Guenter Knauf authored
-
Guenter Knauf authored
-
- Oct 28, 2014
-
-
Guenter Knauf authored
This check works also with to non-configure platforms.
-
Steve Holme authored
-
Steve Holme authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
- Oct 27, 2014
-
-
Daniel Stenberg authored
HTTP 1.1 is clearly specified to only allow three digit response codes, and libcurl used sscanf("%3d") for that purpose. This made libcurl support smaller numbers but not larger. It does now, but we will not make any specific promises nor document this further since it is going outside of what HTTP is. Bug: http://curl.haxx.se/bug/view.cgi?id=1441 Reported-by: Balaji
-
- Oct 26, 2014
-
-
Daniel Stenberg authored
It has not been used since commit f7bfdbab in 2011
-
Steve Holme authored
Continuing commit 0eb3d15c more return code variable name changes.
-
Guenter Knauf authored
-
Steve Holme authored
-
Steve Holme authored
Continuing commit 0eb3d15c more return code variable name changes.
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
Code cleanup to try and synchronise code between the different SSPI based authentication mechanisms.
-
Steve Holme authored
Code cleanup to try and synchronise code between the different SSPI based authentication mechanisms.
-
Steve Holme authored
Don't call CompleteAuthToken() after InitializeSecurityContext() has returned SEC_I_CONTINUE_NEEDED as this return code only indicates the function should be called again after receiving a response back from the server. This only affected the Digest and NTLM authentication code.
-
Dan Fandrich authored
Each shows evidence of flakiness on at least one platform on the autobuilds. Users can use this keyword to skip these tests if desired.
-
Steve Holme authored
For consistency with other areas of the NTLM code propagate all errors from Curl_ntlm_core_mk_nt_hash() up the call stack rather than just CURLE_OUT_OF_MEMORY.
-
Steve Holme authored
-
Steve Holme authored
Continuing commit 0eb3d15c more return code variable name changes.
-
- Oct 25, 2014
-
-
Steve Holme authored
-
Steve Holme authored
Code cleanup to try and synchronise code between the different SSPI based authentication mechanisms.
-
Steve Holme authored
Code cleanup to try and synchronise code between the different SSPI based authentication mechanisms.
-
Steve Holme authored
Code cleanup to try and synchronise code between the different SSPI based authentication mechanisms.
-
Steve Holme authored
Continuing commit 0eb3d15c more return code variable name changes.
-
Steve Holme authored
Added support for WinIDN build configurations to the VC8 and VC9 project files.
-
- Oct 24, 2014
-
-
Nick Zitzmann authored
If Apple ever drops SSLv3 support from the Security framework, we'll fail with an error if the user insists on using SSLv3.
-
Patrick Monnerat authored
-