Revision tags: curl-7_76_1, curl-7_76_0, curl-7_75_0, curl-7_74_0 |
|
#
4d2f8006 |
| 04-Nov-2020 |
Daniel Stenberg |
curl.se: new home Closes #6172
|
Revision tags: curl-7_73_0, tiny-curl-7_72_0, curl-7_72_0, curl-7_71_1, curl-7_71_0, curl-7_70_0, curl-7_69_1, curl-7_69_0, curl-7_68_0, curl-7_67_0, curl-7_66_0, curl-7_65_3, curl-7_65_2, curl-7_65_1, curl-7_65_0, curl-7_64_1, curl-7_64_0, curl-7_63_0, curl-7_62_0, curl-7_61_1, curl-7_61_0, curl-7_60_0, curl-7_59_0, curl-7_58_0, curl-7_57_0, curl-7_56_1, curl-7_56_0, curl-7_55_1, curl-7_55_0, curl-7_54_1, curl-7_54_0, curl-7_53_1, curl-7_53_0 |
|
#
5aef498b |
| 07-Feb-2017 |
Daniel Stenberg |
CHANGES: spell fix, use correct path to script
|
Revision tags: curl-7_52_1, curl-7_52_0, curl-7_51_0, curl-7_50_3, curl-7_50_2, curl-7_50_1, curl-7_50_0, curl-7_49_1, curl-7_49_0, curl-7_48_0, curl-7_47_1 |
|
#
4af40b36 |
| 02-Feb-2016 |
Daniel Stenberg |
URLs: change all http:// URLs to https://
|
Revision tags: curl-7_47_0, curl-7_46_0, curl-7_45_0, curl-7_44_0 |
|
#
8279dd7d |
| 06-Aug-2015 |
Daniel Stenberg |
CHANGES: refer to the online changelog Suggested-by: mc0e
|
Revision tags: curl-7_43_0, curl-7_42_1, curl-7_42_0, curl-7_41_0, curl-7_40_0, curl-7_39_0, curl-7_38_0, curl-7_37_1, curl-7_37_0, curl-7_36_0, curl-7_35_0, curl-7_34_0, curl-7_33_0, curl-7_32_0, curl-7_31_0, curl-7_30_0, curl-7_29_0, curl-7_28_1, curl-7_28_0, curl-7_27_0, curl-7_26_0, curl-7_25_0, curl-7_24_0, curl-7_23_1, curl-7_23_0, curl-7_22_0, curl-7_21_7, curl-7_21_6, curl-7_21_5, curl-7_21_4, curl-7_21_3, curl-7_21_2, curl-7_21_1 |
|
#
a89d7997 |
| 21-Jun-2010 |
Daniel Stenberg |
CHANGES: move all contents from CHANGES to CHANGES.0 CHANGES is no longer used for manually edited content. It is to be generated automatically by maketgz when we make release tarbal
CHANGES: move all contents from CHANGES to CHANGES.0 CHANGES is no longer used for manually edited content. It is to be generated automatically by maketgz when we make release tarballs.
show more ...
|
#
d63bdba0 |
| 17-Jun-2010 |
Kamil Dudka |
test575: do not fail with threaded DNS resolver
|
Revision tags: curl-7_21_0 |
|
#
e91d167f |
| 16-Jun-2010 |
Daniel Stenberg |
release: 7.21.0
|
#
a0dd9df9 |
| 05-Jun-2010 |
Constantine Sapuntzakis |
OpenSSL: fix spurious SSL connection aborts Was seeing spurious SSL connection aborts using libcurl and OpenSSL. I tracked it down to uncleared error state on the OpenSSL error stack
OpenSSL: fix spurious SSL connection aborts Was seeing spurious SSL connection aborts using libcurl and OpenSSL. I tracked it down to uncleared error state on the OpenSSL error stack - patch attached deals with that. Rough idea of problem: Code that uses libcurl calls some library that uses OpenSSL but don't clear the OpenSSL error stack after an error. ssluse.c calls SSL_read which eventually gets an EWOULDBLOCK from the OS. Returns -1 to indicate an error ssluse.c calls SSL_get_error. First thing, SSL_get_error calls ERR_get_error to check the OpenSSL error stack, finds an old error and returns SSL_ERROR_SSL instead of SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE. ssluse.c returns an error and aborts the connection Solution: Clear the openssl error stack before calling SSL_* operation if we're going to call SSL_get_error afterwards. Notes: This is much more likely to happen with multi because it's easier to intersperse other calls to the OpenSSL library in the same thread.
show more ...
|
#
8098d941 |
| 04-Jun-2010 |
Frank Meier |
getinfo: added *_PRIMARY_PORT, *_LOCAL_IP and *_LOCAL_PORT
|
#
43d20d81 |
| 04-Jun-2010 |
Yang Tse |
Enable OpenLDAP support for cygwin builds. Enable OpenLDAP support for cygwin builds. This support was disabled back in 2008 due to incompatibilities between OpenSSL and OpenLDAP headers
Enable OpenLDAP support for cygwin builds. Enable OpenLDAP support for cygwin builds. This support was disabled back in 2008 due to incompatibilities between OpenSSL and OpenLDAP headers. cygwin's OpenSSL 0.9.8l and OpenLDAP 2.3.43 versions on cygwin 1.5.25 allow building an OpenLDAP enabled libcurl supporting back to Windows 95. Remove non-functional CURL_LDAP_HYBRID code and references.
show more ...
|
#
684830cb |
| 02-Jun-2010 |
Daniel Stenberg |
SSH: corrected the inability to respect the timeout Jason McDonald posted bug report #3006786 when he found that the SFTP code didn't timeout properly in several places in the code e
SSH: corrected the inability to respect the timeout Jason McDonald posted bug report #3006786 when he found that the SFTP code didn't timeout properly in several places in the code even if a timeout was set properly. Based on his suggested patch, I wrote a different implementation that I think addressed the issue better and also uses the connect timeout for the initial part of the SSH/SFTP done during the "protocol connect" phase. (http://curl.haxx.se/bug/view.cgi?id=3006786)
show more ...
|
#
51248a9b |
| 02-Jun-2010 |
Yang Tse |
mention last changes
|
#
2c72732e |
| 01-Jun-2010 |
Daniel Stenberg |
multi_socket: handles timer inaccuracy better for timeouts Igor Novoseltsev reported a problem with the multi socket API and using timeouts and timers. It boiled down to a problem with
multi_socket: handles timer inaccuracy better for timeouts Igor Novoseltsev reported a problem with the multi socket API and using timeouts and timers. It boiled down to a problem with libcurl's use of GetTickCount() interally to figure out the current time, while Igor's own application code used another function call. It made his app call the socket API timeout function a bit _before_ libcurl would consider the timeout to trigger, and that could easily lead to timeouts or stalls in the app. It seems GetTickCount() in general often has no better resolution than 16ms and switching to the alternative function QueryPerformanceCounter has its share of problems: http://www.virtualdub.org/blog/pivot/entry.php?id=106 We address this problem by simply having libcurl treat timers that already has occured or will occur within 40ms subject for treatment. I'm confident that there are other implementations and operating systems with similarly in accurate timer functions so it makes sense to have applied generically and I don't believe we sacrifice much by adding a 40ms inaccuracy on these timeouts.
show more ...
|
#
01459828 |
| 27-May-2010 |
Kamil Dudka |
test313: a new test for CRL support
|
#
b4f0e129 |
| 27-May-2010 |
Tor Arntsen |
setup_once: use enum type for 'bool' on non-C99 platforms An enum will catch non-bool assignments to bool on platforms with a strict compiler, e.g MIPSPro. Signed-off-by: Kamil
setup_once: use enum type for 'bool' on non-C99 platforms An enum will catch non-bool assignments to bool on platforms with a strict compiler, e.g MIPSPro. Signed-off-by: Kamil Dudka <kdudka@redhat.com>
show more ...
|
#
d3c813e7 |
| 25-May-2010 |
Julien Chaffraix |
RTMP: Fix compiler warnings
|
#
9e480973 |
| 25-May-2010 |
Julien Chaffraix |
OOM fixes in http_negociate.c and lib/splay.c Fix 2 OOM errors: a missing NULL-check in lib/http_negociate.c and a potential NULL dereferencing in lib/splay.c
|
#
2e056353 |
| 24-May-2010 |
Howard Chu |
LDAP: properly implemented as a curl_handler makes the LDAP code much cleaner, nicer and in general being a better libcurl citizen. If a new enough OpenLDAP version is detect, the ne
LDAP: properly implemented as a curl_handler makes the LDAP code much cleaner, nicer and in general being a better libcurl citizen. If a new enough OpenLDAP version is detect, the new and shiny lib/openldap.c code is then used instead of the old cruft Code by Howard, minor cleanups by Daniel.
show more ...
|
#
d17709da |
| 21-May-2010 |
Daniel Stenberg |
TFTP: send legal timeout value Eric Mertens posted bug #3003705: when we made TFTP use the correct timeout option when sent to the server (fixed May 18th 2010) it became obvious that
TFTP: send legal timeout value Eric Mertens posted bug #3003705: when we made TFTP use the correct timeout option when sent to the server (fixed May 18th 2010) it became obvious that libcurl used invalid timeout values (300 by default while the RFC allows nothing above 255). While of course it is obvious that as TFTP has worked thus far without being able to set timeout at all, just removing the setting wouldn't make any difference in behavior. I decided to still keep it (but fix the problem) as it now actually allows for easier (future) customization of the timeout. (http://curl.haxx.se/bug/view.cgi?id=3003705)
show more ...
|
#
0a29e244 |
| 21-May-2010 |
Daniel Stenberg |
TFTP: block id wrap bug fix In a normal expression, doing [unsigned short] + 1 will not wrap at 16 bits so the comparisons and outputs were done wrong. I added a macro do make sure i
TFTP: block id wrap bug fix In a normal expression, doing [unsigned short] + 1 will not wrap at 16 bits so the comparisons and outputs were done wrong. I added a macro do make sure it gets done right. Douglas Kilpatrick filed bug report #3004787 about it: http://curl.haxx.se/bug/view.cgi?id=3004787
show more ...
|
#
81239edb |
| 20-May-2010 |
Tanguy Fautre |
build: allow curl to build with Microsoft VC10 By undefing a bunch of E* defines that VC10 has started to define but that we redefine internally to their WSA* alternatives when build
build: allow curl to build with Microsoft VC10 By undefing a bunch of E* defines that VC10 has started to define but that we redefine internally to their WSA* alternatives when building for Windows.
show more ...
|
#
aabd27d9 |
| 18-May-2010 |
Daniel Stenberg |
TFTP: send timeout option correctly Eric Mertens posted bug report #3003005 pointing out that the libcurl TFTP code was not sending the timeout option properly to the server, and sug
TFTP: send timeout option correctly Eric Mertens posted bug report #3003005 pointing out that the libcurl TFTP code was not sending the timeout option properly to the server, and suggested a fix. (http://curl.haxx.se/bug/view.cgi?id=3003005)
show more ...
|
#
2ffe834b |
| 16-May-2010 |
Kamil Dudka |
ftp wildcard: a new option CURLOPT_FNMATCH_DATA
|
#
77cfeadf |
| 14-May-2010 |
Daniel Stenberg |
OpenSSL: multi interface handshake could hang John-Mark Bell filed bug #3000052 that identified a problem (with an associated patch) with the OpenSSL handshake state machine when the
OpenSSL: multi interface handshake could hang John-Mark Bell filed bug #3000052 that identified a problem (with an associated patch) with the OpenSSL handshake state machine when the multi interface is used: Performing an https request using a curl multi handle and using select or epoll to wait for events results in a hang. It appears that the cause is the fix for bug #2958179, which makes ossl_connect_common unconditionally return from the step 2 loop when fetching from a multi handle. When ossl_connect_step2 has completed, it updates connssl->connecting_state to ssl_connect_3. ossl_connect_common will then return to the caller, as a multi handle is in use. Eventually, the client code will call curl_multi_fdset to obtain an updated fdset to select or epoll on. For https requests, curl_multi_fdset will cause https_getsock to be called. https_getsock will only return a socket handle if the connecting_state is ssl_connect_2_reading or ssl_connect_2_writing. Therefore, the client will never obtain a valid fdset, and thus not drive the multi handle, resulting in a hang. (http://curl.haxx.se/bug/view.cgi?id=3000052)
show more ...
|
#
ea521cf6 |
| 14-May-2010 |
Daniel Stenberg |
changelog: add link to bug report
|