- Mar 30, 2017
-
-
Marcel Raad authored
When CURL_DISABLE_VERBOSE_STRINGS is defined, the reason parameter in Curl_conncontrol is not used as the infof macro expands to nothing.
-
Marcel Raad authored
At least under Windows, there is no SIZEOF_LONG, so it evaluates to 0 even though sizeof(int) == sizeof(long). This should probably have been CURL_SIZEOF_LONG, but the type of timeout_ms changed from long to time_t anyway. This triggered MSVC warning C4668 about implicitly replacing undefined macros with '0'. Closes https://github.com/curl/curl/pull/1362
-
- Mar 29, 2017
-
-
Marcel Raad authored
Feature defines are normally checked with #ifdef instead of #if in the rest of the codebase. Additionally, some compilers warn when a macro is implicitly evaluated to 0 because it is not defined, which was the case here. Ref: https://github.com/curl/curl/pull/1362#discussion_r108605101 Closes https://github.com/curl/curl/pull/1367
-
- Mar 28, 2017
-
-
Daniel Stenberg authored
... to make it much faster. Idea developed with primepie on IRC. Closes #1365
-
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>
-
- 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]
-
- Mar 26, 2017
-
-
klemens authored
Closes #1356
-
- Mar 23, 2017
-
-
Daniel Stenberg authored
-
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
-
- Mar 22, 2017
- Mar 21, 2017
-
-
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 18, 2017
-
-
Palo Markovic authored
Broken a week ago in 6448f98c. Closes https://github.com/curl/curl/pull/1337
-
- Mar 13, 2017
-
-
Sylvestre Ledru authored
... by removing the else branch after a return, break or continue. Closes #1310
-
- Mar 12, 2017
-
-
Desmond O. Chang authored
- Add new option CURLOPT_SUPPRESS_CONNECT_HEADERS to allow suppressing proxy CONNECT response headers from the user callback functions CURLOPT_HEADERFUNCTION and CURLOPT_WRITEFUNCTION. - Add new tool option --suppress-connect-headers to expose CURLOPT_SUPPRESS_CONNECT_HEADERS and allow suppressing proxy CONNECT response headers from --dump-header and --include. Assisted-by: Jay Satiro Assisted-by: <CarloCannas@users.noreply.github.com> Closes https://github.com/curl/curl/pull/783
-
- Mar 11, 2017
-
-
Jay Satiro authored
A client MUST ignore any Content-Length or Transfer-Encoding header fields received in a successful response to CONNECT. "Successful" described as: 2xx (Successful). RFC 7231 4.3.6 Prior to this change such a case would cause an error. In some ways this bug appears to be a regression since c50b878c. Prior to that libcurl may have appeared to function correctly in such cases by acting on those headers instead of causing an error. But that behavior was also incorrect. Bug: https://github.com/curl/curl/issues/1317 Reported-by: <mkzero@users.noreply.github.com>
-
Thomas Glanzmann authored
Broken a few days ago in 6448f98c. Bug: https://curl.haxx.se/mail/lib-2017-03/0015.html
-
Michael Kaufmann authored
This prevents a "Descriptor is not a socket" error for WinSSL. Reported-by: <Antony74@users.noreply.github.com> Reviewed-by: Jay Satiro Fixes https://github.com/curl/curl/issues/1239
-
Michael Kaufmann authored
Follow-up to 5278462c See https://github.com/curl/curl/issues/1095
-
Isaac Boukris authored
This flag is meant for the current request based on authentication state, once the request is done we can clear the flag. Also change auth.multi to auth.multipass for better readability. Fixes https://github.com/curl/curl/issues/1095 Closes https://github.com/curl/curl/pull/1326 Signed-off-by: Isaac Boukris <iboukris@gmail.com> Reported-by: Michael Kaufmann
-
Dan Fandrich authored
-
- Mar 10, 2017
-
-
Daniel Stenberg authored
CID 1402159 and 1402158
-
- Mar 09, 2017
-
-
Dan Fandrich authored
-
- Mar 08, 2017
-
-
Daniel Stenberg authored
Verified with OpenSSL 1.1.0e and OpenSSL master (1.1.1)
-
Jozef Kralik authored
This commit introduces the CURL_SSLVERSION_MAX_* constants as well as the --tls-max option of the curl tool. Closes https://github.com/curl/curl/pull/1166
-
- Mar 07, 2017
-
-
Tatsuhiro Tsujikawa authored
This fixes assertion error which occurs when redirect is done with 0 length body via HTTP/2, and the easy handle is reused, but new connection is established due to hostname change: curl: http2.c:1572: ssize_t http2_recv(struct connectdata *, int, char *, size_t, CURLcode *): Assertion `httpc->drain_total >= data->state.drain' failed. To fix this bug, ensure that http2_handle_stream is called. Fixes #1286 Closes #1302
-
Daniel Stenberg authored
-
Daniel Stenberg authored
Assisted-by: Ray Satiro Bug: https://curl.haxx.se/mail/lib-2017-03/0009.html
-
- Mar 06, 2017
-
-
Daniel Stenberg authored
... because it causes confusion with users. Example URLs: "http://[127.0.0.1]:11211:80" which a lot of languages' URL parsers will parse and claim uses port number 80, while libcurl would use port number 11211. "http://user@example.com:80@localhost" which by the WHATWG URL spec will be treated to contain user name 'user@example.com' but according to RFC3986 is user name 'user' for the host 'example.com' and then port 80 is followed by "@localhost" Both these formats are now rejected, and verified so in test 1260. Reported-by: Orange Tsai
-
Daniel Stenberg authored
Pointed-out-by: Ray Satiro Bug: https://curl.haxx.se/mail/lib-2017-03/0004.html
-
- Mar 05, 2017
-
-
Michael Maltese authored
Assisted-by: Simon Warta <simon@kullo.net> Ref: https://github.com/curl/curl/pull/1228
-
- Mar 04, 2017
-
-
Andrew Krieger authored
MSVC with LTCG detects this at warning level 4. Closes #1304
-
- Mar 03, 2017
-
-
Jay Satiro authored
Move the proxy parse/init into helper create_conn_helper_init_proxy to mitigate the chances some non-proxy code will be mistakenly added to it. Ref: https://github.com/curl/curl/issues/1274#issuecomment-281556510 Ref: https://github.com/curl/curl/pull/1293 Closes https://github.com/curl/curl/pull/1298
-
Alexis La Goutte authored
Mark intended fallthroughs with /* FALLTHROUGH */ so that gcc will know it's expected and won't warn on [-Wimplicit-fallthrough=]. Closes https://github.com/curl/curl/pull/1297
-
- Mar 02, 2017
-
-
Joel Depooter authored
In DarwinSSL the SSLSetPeerDomainName function is used to enable both sending SNI and verifying the host. When host verification is disabled the function cannot be called, therefore SNI is disabled as well. Closes https://github.com/curl/curl/pull/1240
-
- Feb 28, 2017
-
-
Marcel Raad authored
If size_t is 32 bits, MSVC warns: warning C4310: cast truncates constant value The warning is harmless as CURL_MASK_SCOFFT gets truncated to the maximum value of size_t.
-