- Mar 28, 2017
-
-
Kamil Dudka authored
If we use FTPS over CONNECT, the TLS handshake for the FTPS control connection needs to be initiated in the SENDPROTOCONNECT state, not the WAITPROXYCONNECT state. Otherwise, if the TLS handshake completed without blocking, the information about the completed TLS handshake would be saved to a wrong flag. Consequently, the TLS handshake would be initiated in the SENDPROTOCONNECT state once again on the same connection, resulting in a failure of the TLS handshake. I was able to observe the failure with the NSS backend if curl ran through valgrind. Note that this commit partially reverts curl-7_21_6-52-ge34131d.
-
Daniel Stenberg authored
When receiving chunked encoded data with trailers, and the write callback returns PAUSE, there might be both body and header to store to resend on unpause. Previously libcurl returned error for that case. Added test case 1540 to verify. Reported-by: Stephen Toub Fixes #1354 Closes #1357
-
Isaac Boukris authored
When using basic-auth, connections and proxy connections can be re-used with different Authorization headers since it does not authenticate the connection (like NTLM does). For instance, the below command should re-use the proxy connection, but it currently doesn't: curl -v -U alice:a -x http://localhost:8181 http://localhost/ --next -U bob:b -x http://localhost:8181 http://localhost/ This is a regression since refactoring of ConnectionExists() as part of: cb4e2be7 Fix the above by removing the username and password compare when re-using proxy connection at proxy_info_matches(). However, this fix brings back another bug would make curl to re-print the old proxy-authorization header of previous proxy basic-auth connection because it wasn't cleared. For instance, in the below command the second request should fail if the proxy requires authentication, but would succeed after the above fix (and before aforementioned commit): curl -v -U alice:a -x http://localhost:8181 http://localhost/ --next -x http://localhost:8181 http://localhost/ Fix this by clearing conn->allocptr.proxyuserpwd after use unconditionally, same as we do for conn->allocptr.userpwd. Also fix test 540 to not expect digest auth header to be resent when connection is reused. Signed-off-by: Isaac Boukris <iboukris@gmail.com> Closes https://github.com/curl/curl/pull/1350
-
Jay Satiro authored
- Fix compile errors that occur in openssl.c when OpenSSL lib was built without DSA support. Bug: https://github.com/curl/curl/issues/1361 Reported-by: <neheb@users.noreply.github.com>
-
Jay Satiro authored
-
- Mar 27, 2017
-
-
Marcel Raad authored
No need to redeclare the variable.
-
Marcel Raad authored
error: conversion to 'long int' from 'time_t {aka long long int}' may alter its value [-Werror=conversion]
-
Marcel Raad authored
If Makefile.am uses CRLF, buildconf in a Windows checkout fails with: ".ibtoolize: error: AC_CONFIG_MACRO_DIRS([m4]) conflicts with ACLOCAL_AMFLAGS=-I m4"
-
- Mar 26, 2017
-
-
klemens authored
Closes #1356
-
- Mar 25, 2017
-
-
Daniel Stenberg authored
Reported-by: Brian Carpenter Added test 1442 to verify
-
- Mar 24, 2017
-
-
Marcel Raad authored
curl must be built before building the tests. Closes https://github.com/curl/curl/pull/1352
-
- Mar 23, 2017
-
-
Daniel Stenberg authored
-
Edward Kimmel authored
Send curl_socket_t to event_cb and make sure it hasn't been closed yet. Closes https://github.com/curl/curl/pull/1318
-
Dan Fandrich authored
-
Jay Satiro authored
- If SSL_get_error is called but no extended error detail is available then show that SSL_ERROR_* as a string. Prior to this change there was some inconsistency in that case: the SSL_ERROR_* code may or may not have been shown, or may have been shown as unknown even if it was known. Ref: https://github.com/curl/curl/issues/1300 Closes https://github.com/curl/curl/pull/1348
-
Dan Fandrich authored
This is nowadays included with the base perl distribution, but wasn't prior to about perl 5.14
-
Anders Roxell authored
Signed-off-by: Anders Roxell <anders.roxell@gmail.com> Closes #1342
-
- Mar 22, 2017
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
Running this in the root build dir will invoke the test suite to only run tests not marked as 'flaky'.
-
Daniel Stenberg authored
-
- Mar 21, 2017
-
-
Peter Wu authored
Note that for some reason there is this warning (that also exists with autotools, added since curl-7_15_1-94-ga718cb05f): docs/libcurl/curl_multi_socket_all.3:1: can't open `man3/curl_multi_socket.3': No such file or directory Additionally, adjust the roffit --mandir option to support creating links when doing out-of-tree builds. Ref: https://github.com/curl/curl/pull/1288
-
Peter Wu authored
Also make Perl mandatory to allow building the docs. While CMakeLists.txt could probably read the list of manual pages from Makefile.am, actually putting those in CMakeLists.txt is cleaner so that is what is done here. Fixes #1230 Ref: https://github.com/curl/curl/pull/1288
-
Peter Wu authored
For easier sharing with CMake. The contents were reformatted to use two-space indent and expanded tabs (matching lib/Makefile.common). Ref: https://github.com/curl/curl/pull/1288
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
The code would refer to the wrong data pointer. Only debug builds do this - for verbosity. Reported-by: <zelinchen@users.noreply.github.com> Fixes #1329
-
- Mar 20, 2017
-
-
Daniel Stenberg authored
-
Dan Fandrich authored
-
Dan Fandrich authored
-
Dan Fandrich authored
These tests use an HTTP proxy so require that curl be built with HTTP support.
-
Dan Fandrich authored
The CURLOPT_USERAGENT and CURLOPT_MAXREDIRS options are only set if HTTP support is available, so ignore them in tests where HTTP is not guaranteed.
-
- Mar 18, 2017
-
-
Palo Markovic authored
Broken a week ago in 6448f98c. Closes https://github.com/curl/curl/pull/1337
-
- Mar 16, 2017
-
-
Jay Satiro authored
- Show the HTTPS-proxy options on CURLE_SSL_CACERT if libcurl was built with HTTPS-proxy support. Prior to this change those options were shown only if an HTTPS-proxy was specified by --proxy, but that did not take into account environment variables such as http_proxy, https_proxy, etc. Follow-up to e1187c42. Bug: https://github.com/curl/curl/issues/1331 Reported-by: Nehal J Wani
-
Jay Satiro authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
- Mar 15, 2017
-
-
Daniel Stenberg authored
-