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
ce1a58414a
curl/RELEASE-NOTES

38 lines
1.1 KiB
Plaintext
Raw Normal View History

start climbing to 7.19.6
2009-05-18 03:58:00 -04:00
Curl and libcurl 7.19.6
working draft of the upcoming 7.10.8 release notes
2003-09-22 17:38:52 -04:00
start climbing to 7.19.6
2009-05-18 03:58:00 -04:00
Public curl releases: 112
- Craig A West brought us: libcurl now defaults to do CONNECT with HTTP version 1.1 instead of 1.0 like before. This change also introduces the new proxy type for libcurl called 'CURLPROXY_HTTP_1_0' that then allows apps to switch (back) to CONNECT 1.0 requests. The curl tool also got a --proxy1.0 option that works exactly like --proxy but sets CURLPROXY_HTTP_1_0. I updated all test cases cases that use CONNECT and I tried to do some using --proxy1.0 and some updated to do CONNECT 1.1 to get both versions run.
2009-02-02 11:19:23 -05:00
Command line options: 132
- David Kierznowski notified us about a security flaw (http://curl.haxx.se/docs/adv_20090303.html also known as CVE-2009-0037) in which previous libcurl versions (by design) can be tricked to access an arbitrary local/different file instead of a remote one when CURLOPT_FOLLOWLOCATION is enabled. This flaw is now fixed in this release together this the addition of two new setopt options for controlling this new behavior: o CURLOPT_REDIR_PROTOCOLS controls what protocols libcurl is allowed to follow to when CURLOPT_FOLLOWLOCATION is enabled. By default, this option excludes the FILE and SCP protocols and thus you nee to explicitly allow them in your app if you really want that behavior. o CURLOPT_PROTOCOLS controls what protocol(s) libcurl is allowed to fetch using the primary URL option. This is useful if you want to allow a user or other outsiders control what URL to pass to libcurl and yet not allow all protocols libcurl may have been built to support.
2009-03-02 18:05:31 -05:00
curl_easy_setopt() options: 163
- 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
the Eiffel binding
2009-03-02 04:03:11 -05:00
Known libcurl bindings: 38
15 additional contributor from the 7.19.4 RELEASE-NOTES
2009-03-03 05:41:11 -05:00
Contributors: 715
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
start climbing to 7.19.6
2009-05-18 03:58:00 -04:00
o
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:
- Kamil Dudka brought the patch from the Redhat bug entry https://bugzilla.redhat.com/show_bug.cgi?id=427966 which was libcurl closing a bad file descriptor when closing down the FTP data connection. Caolan McNamara seems to be the original author of it.
2009-05-19 16:54:31 -04:00
o crash on bad socket close with FTP
- bug report #2796358 (http://curl.haxx.se/bug/view.cgi?id=2796358) pointed out that the cookie parser would leak memory when it parses cookies that are received with domain, path etc set multiple times in the same header. While such a cookie is questionable, they occur in the wild and libcurl no longer leaks memory for them. I added such a header to test case 8.
2009-05-25 08:23:22 -04:00
o leaking cookie memory when duplicate domains or paths were used
- Frank McGeough provided a small OpenSSL #include fix to make libcurl compile fine with Nokia 5th edition 1.0 SDK for Symbian.
2009-05-27 17:11:11 -04:00
o build fix for Symbian
- Mike Crowe pointed out that setting CURLOPT_USERPWD to NULL used to clear the auth credentials back in 7.19.0 and earlier while now you have to set "" to get the same effect. His patch brings back the ability to use NULL.
2009-05-27 17:45:12 -04:00
o CURLOPT_USERPWD set to NULL clears auth credentials
- Claes Jakobsson fixed the configure script to better find and use NSS without pkg-config.
2009-06-01 05:40:09 -04:00
o libcurl-NSS build fixes
- Claes Jakobsson fixed libcurl-NSS to build fine even without the PK11_CreateGenericObject() function.
2009-05-27 18:01:03 -04:00
o libcurl-NSS build fix
credit John E. Malmberg
2009-06-01 05:20:49 -04:00
o configure script fixed for VMS
- Setting the Content-Length: header from your app when you do a POST or PUT is almost always a VERY BAD IDEA. Yet there are still apps out there doing this, and now recently it triggered a bug/side-effect in libcurl as when libcurl sends a POST or PUT with NTLM, it sends an empty post first when it knows it will just get a 401/407 back. If the app then replaced the Content-Length header, it caused the server to wait for input that libcurl wouldn't send. Aaron Oneal reported this problem in bug report #2799008 http://curl.haxx.se/bug/view.cgi?id=2799008) and helped us verify the fix.
2009-06-05 02:18:42 -04:00
o set Content-Length: with POST and PUT failed with NTLM auth
allow building libcurl for VxWorks
2009-06-04 15:11:11 -04:00
o allow building libcurl for VxWorks
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:
- Setting the Content-Length: header from your app when you do a POST or PUT is almost always a VERY BAD IDEA. Yet there are still apps out there doing this, and now recently it triggered a bug/side-effect in libcurl as when libcurl sends a POST or PUT with NTLM, it sends an empty post first when it knows it will just get a 401/407 back. If the app then replaced the Content-Length header, it caused the server to wait for input that libcurl wouldn't send. Aaron Oneal reported this problem in bug report #2799008 http://curl.haxx.se/bug/view.cgi?id=2799008) and helped us verify the fix.
2009-06-05 02:18:42 -04:00
Yang Tse, Daniel Fandrich, Kamil Dudka, Caolan McNamara, Frank McGeough,
Andre Guibert de Bruet, Mike Crowe, Claes Jakobsson, John E. Malmberg,
remove conflict markers
2009-06-05 02:19:29 -04:00
Aaron Oneal, 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