moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-12-22 16:18:48 -05:00
Code Issues Releases Wiki Activity
2c72732ebf
curl/RELEASE-NOTES

51 lines
1.8 KiB
Plaintext
Raw Normal View History

changelogs: mention RTMP and the FTP wildcard support
2010-05-12 18:00:55 -04:00
Curl and libcurl 7.21.0
working draft of the upcoming 7.10.8 release notes
2003-09-22 17:38:52 -04:00
bumped to start the journey towards 7.20.2
2010-04-14 11:34:26 -04:00
Public curl releases: 116
RELEASE-NOTES: update top numbers
2010-04-24 06:23:47 -04:00
Command line options: 138
ftp wildcard: a new option CURLOPT_FNMATCH_DATA
2010-05-15 20:49:08 -04:00
curl_easy_setopt() options: 180
- Introducing curl_easy_send() and curl_easy_recv(). They can be used to send and receive data over a connection previously setup with curl_easy_perform() and its CURLOPT_CONNECT_ONLY option. The sendrecv.c example was added to show how they can be used.
2008-05-12 17:43:24 -04:00
Public functions in libcurl: 58
a binding for Falcon
2009-11-29 14:12:00 -05:00
Known libcurl bindings: 39
RELEASE-NOTES: update top numbers
2010-04-24 06:23:47 -04:00
Contributors: 794
David Hull made the file: URL parser also accept the somewhat sloppy file syntax: file:/path. I added test case 203 to verify this.
2003-10-29 04:53:21 -05:00
Armel Asselin made the CURLOPT_PREQUOTE option work fine even when CURLOPT_NOBODY is set true. PREQUOTE is then run roughly at the same place in the command sequence as it would have run if there would've been a transfer.
2006-08-08 18:56:46 -04:00
This release includes the following changes:
mention the curl_off_t changes first
2008-09-01 10:27:24 -04:00
changelog: added the --proto and -proto-redir options
2010-04-24 06:19:42 -04:00
o added the --proto and -proto-redir options
new configure option --enable-threaded-resolver
2010-04-25 17:24:05 -04:00
o new configure option --enable-threaded-resolver
changelog: mention Ben Greear's telnet work
2010-04-29 03:40:48 -04:00
o improve TELNET ability with libcurl
changelog: PolarSSL
2010-05-05 16:36:15 -04:00
o added support for PolarSSL
changelogs: mention RTMP and the FTP wildcard support
2010-05-12 18:00:55 -04:00
o added support for FTP wildcard matching and downloads
o added support for RTMP
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.
2010-05-24 18:44:42 -04:00
o introducing new LDAP code for new enough OpenLDAP
Armel Asselin made the CURLOPT_PREQUOTE option work fine even when CURLOPT_NOBODY is set true. PREQUOTE is then run roughly at the same place in the command sequence as it would have run if there would've been a transfer.
2006-08-08 18:56:46 -04:00
HTTP Digest auth fix on a re-used connection
2007-07-22 06:17:52 -04:00
This release includes the following bugfixes:
changelog: prevent needless reverse name lookups
2010-04-15 07:11:25 -04:00
o prevent needless reverse name lookups
changelog: GnuTLS fix, no reverse loopkups and fixed GSS detection
2010-04-16 09:33:10 -04:00
o detect GSS on ancient Linux distros
o GnuTLS: EOF caused error when it wasn't
changelog: GnuTLS: SSL handshake phase is non-blocking
2010-04-16 16:45:06 -04:00
o GnuTLS: SSL handshake phase is non-blocking
changelog: -J/--remote-header-name strips CRLF
2010-04-19 11:08:27 -04:00
o -J/--remote-header-name strips CRLF
replaced wsock32.lib usage with ws2_32.lib in MSVC makefiles
2010-04-20 10:30:10 -04:00
o MSVC makefiles now use ws2_32.lib instead of wsock32.lib
curl: -O crash on windows The -O option caused curl to crash on windows and DOS due to the tool writing out of boundary memory.
2010-04-21 17:20:18 -04:00
o -O crash on windows
nss: fix SSL handshake timeout underflow
2010-04-24 17:21:13 -04:00
o SSL handshake timeout underflow in libcurl-NSS
multi interface: missed storing connection time Dirk Manske reported a regression. When connecting with the multi interface, there were situations where libcurl wouldn't store connect time correctly as it used to (and is documented to) do. Using his fine sample program we could repeat it, and I wrote up test case 573 using that code. The problem does not easily show itself using the local test suite though. The fix, also as suggested by Dirk, is a bit on the ugly side as it adds yet another call to Curl_verboseconnect() and setting the TIMER_CONNECT time. That situation is subject for some closer inspection in the future.
2010-05-07 17:49:29 -04:00
o multi interface missed storing connection time
changelog: fixed CRL support in libcurl-NSS
2010-05-11 08:51:12 -04:00
o broken CRL support in libcurl-NSS
follow redirect: ignore response-body on redirect even if compressed Sebastian V reported bug #3000056 identifying a problem with redirect following. It showed that when curl followed redirects it didn't properly ignore the response body of the 30X response if that response was using compressed Content-Encoding! (http://curl.haxx.se/bug/view.cgi?id=3000056)
2010-05-14 16:12:07 -04:00
o ignore response-body on redirect even if compressed
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)
2010-05-14 16:34:10 -04:00
o OpenSSL handshake state-machine for multi interface
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)
2010-05-18 17:14:00 -04:00
o TFTP timeout option sent correctly
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
2010-05-21 17:04:15 -04:00
o TFTP block id wrap
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.
2010-06-01 17:18:34 -04:00
o curl_multi_socket_action() timeout handles inaccuracy in timers better
HTTP Digest auth fix on a re-used connection
2007-07-22 06:17:52 -04:00
This release includes the following known bugs:
o see docs/KNOWN_BUGS (http://curl.haxx.se/docs/knownbugs.html)
This release would not have looked like this without help, code, reports and
advice from friends like these:
changelog: mention Ben Greear's telnet work
2010-04-29 03:40:48 -04:00
Rainer Canavan, Paul Howarth, Jerome Vouillon, Ruslan Gazizov, Yang Tse,
changelogs: mention RTMP and the FTP wildcard support
2010-05-12 18:00:55 -04:00
Kamil Dudka, Alex Bligh, Ben Greear, Hoi-Ho Chan, Howard Chu, Dirk Manske,
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.
2010-06-01 17:18:34 -04:00
Pavel Raiskup, John-Mark Bell, Eric Mertens, Tor Arntsen, Douglas Kilpatrick,
Igor Novoseltsev
start over on 7.18.1
2008-01-28 16:19:15 -05:00
working draft of the upcoming 7.10.8 release notes
2003-09-22 17:38:52 -04:00
Thanks! (and sorry if I forgot to mention someone)
Reference in New Issue Copy Permalink