moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-12-21 23:58:49 -05:00
Code Issues Releases Wiki Activity
f5e85bab1c
curl/RELEASE-NOTES

44 lines
1.7 KiB
Plaintext
Raw Normal View History

start working on 7.15.1
2005-10-13 05:23:51 -04:00
Curl and libcurl 7.15.1
working draft of the upcoming 7.10.8 release notes
2003-09-22 17:38:52 -04:00
start working on 7.15.1
2005-10-13 05:23:51 -04:00
Public curl release number: 91
Releases counted from the very beginning: 118
mention the recent improvements
2005-09-04 18:10:03 -04:00
Available command line options: 109
Bradford Bruce made the windows resolver code properly return CURLE_COULDNT_RESOLVE_PROXY and CURLE_COULDNT_RESOLVE_HOST on resolving errors (as documented).
2005-10-21 15:21:19 -04:00
Available curl_easy_setopt() options: 125
with all external functions marked with CURL_EXTERN it is easy to count them and... yes, they are 46!
2004-11-09 09:42:04 -05:00
Number of public functions in libcurl: 46
multi IP socket description leak with multi interface
2005-10-25 10:05:21 -04:00
Amount of public web site mirrors: 27
recent changes
2005-09-16 17:03:26 -04:00
Number of known libcurl bindings: 32
start working on 7.15.1
2005-10-13 05:23:51 -04:00
Number of contributors: 459
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
working draft of the upcoming 7.10.8 release notes
2003-09-22 17:38:52 -04:00
This release includes the following changes:
Adrian Schuur added trailer support in the chunked encoding stream. The trailer is then sent to the normal header callback/stream.
2005-07-12 14:15:34 -04:00
Vilmos Nebehaj improved libcurl's LDAP abilities: The LDAP code in libcurl can't handle LDAP servers of LDAPv3 nor binary attributes in LDAP objects. So, I made a quick patch to address these problems. The solution is simple: if we connect to an LDAP server, first try LDAPv3 (which is the preferred protocol as of now) and then fall back to LDAPv2. In case of binary attributes, we first convert them to base64, just like the openldap client does. It uses ldap_get_values_len() instead of ldap_get_values() to be able to retrieve binary attributes correctly. I defined the necessary LDAP macros in lib/ldap.c to be able to compile libcurl without the presence of libldap
2005-10-31 03:55:01 -05:00
o LDAPv3 is now the preferred LDAP protocol version
--max-redirs 0
2005-10-29 18:22:18 -04:00
o --max-redirs and CURLOPT_MAXREDIRS set to 0 limits redirects
Temprimus improved the MSVC makefile so that the static debug SSL libs are linked to the executable and not to the libcurld.lib http://curl.haxx.se/bug/view.cgi?id=1326676
2005-10-21 15:32:12 -04:00
o improved MSVC makefile
working draft of the upcoming 7.10.8 release notes
2003-09-22 17:38:52 -04:00
This release includes the following bugfixes:
Vilmos Nebehaj improved libcurl's LDAP abilities: The LDAP code in libcurl can't handle LDAP servers of LDAPv3 nor binary attributes in LDAP objects. So, I made a quick patch to address these problems. The solution is simple: if we connect to an LDAP server, first try LDAPv3 (which is the preferred protocol as of now) and then fall back to LDAPv2. In case of binary attributes, we first convert them to base64, just like the openldap client does. It uses ldap_get_values_len() instead of ldap_get_values() to be able to retrieve binary attributes correctly. I defined the necessary LDAP macros in lib/ldap.c to be able to compile libcurl without the presence of libldap
2005-10-31 03:55:01 -05:00
o binary LDAP properties are now shown base64 encoded
tommink[at]post.pl reported in bug report #1337723 (http://curl.haxx.se/bug/view.cgi?id=1337723) that curl could not upload binary data from stdin on Windows if the data contained control-Z (hex 1a) since that is treated as end-of-file when read in text mode. Gisle Vanem pointed out the fix, and I made both -T and --data-binary take advantage of it.
2005-10-27 17:02:01 -04:00
o Windows uploads from stdin using curl can now contain ctrl-Z bytes
Jaz Fresh pointed out that if you used "-r [number]" as was wrongly described in the man page, curl would send an invalid HTTP Range: header. The correct way would be to use "-r [number]-" or even "-r -[number]". Starting now, curl will warn if this is discovered, and automatically append a dash to the range before passing it to libcurl.
2005-10-27 08:05:36 -04:00
o -r [num] would produce an invalid HTTP Range: header
multi IP socket description leak with multi interface
2005-10-25 10:05:21 -04:00
o multi interface with multi IP hosts could leak socket descriptors
o the GnuTLS code didn't handle rehandshakes
o re-use of a dead FTP connection
Bradford Bruce made the windows resolver code properly return CURLE_COULDNT_RESOLVE_PROXY and CURLE_COULDNT_RESOLVE_HOST on resolving errors (as documented).
2005-10-21 15:21:19 -04:00
o name resolve error codes fixed for Windows builds
Dave Dribin made libcurl understand and handle cases when the server (wrongly) sends *two* WWW-Authenticate headers for Digest. While this should never happen in a sane world, libcurl previously got into an infinite loop when this occurred. Dave added test 273 to verify this.
2005-10-20 16:07:32 -04:00
o double WWW-Authenticate Digest headers are now handled
Reverted the LIBCURL_VERSION_NUM change from October 6. As Dave Dribin reported, the define is used by the configure script and is assumed to use the 0xYYXXZZ format. This made "curl-config --vernum" fail in the 7.15.0 release version.
2005-10-14 17:21:51 -04:00
o curl-config --vernum fixed
working draft of the upcoming 7.10.8 release notes
2003-09-22 17:38:52 -04:00
Other curl-related news since the previous public release:
multi IP socket description leak with multi interface
2005-10-25 10:05:21 -04:00
o http://curl.nedmirror.nl is a new mirror in Amsterdam, the Netherlands
2 mirrors, 1 binding release
2005-10-20 15:40:30 -04:00
o http://curl.mirror-server.net is a new mirror in Nuremberg, Germany
o http://curl.hoxt.com is a new mirror in Florida, US
o pycurl 7.15.0 was released http://pycurl.sf.net
working draft of the upcoming 7.10.8 release notes
2003-09-22 17:38:52 -04:00
This release would not have looked like this without help, code, reports and
advice from friends like these:
Jaz Fresh pointed out that if you used "-r [number]" as was wrongly described in the man page, curl would send an invalid HTTP Range: header. The correct way would be to use "-r [number]-" or even "-r -[number]". Starting now, curl will warn if this is discovered, and automatically append a dash to the range before passing it to libcurl.
2005-10-27 08:05:36 -04:00
Dave Dribin, Bradford Bruce, Temprimus, Ofer, Dima Barsky, Amol Pattekar, Jaz
Vilmos Nebehaj improved libcurl's LDAP abilities: The LDAP code in libcurl can't handle LDAP servers of LDAPv3 nor binary attributes in LDAP objects. So, I made a quick patch to address these problems. The solution is simple: if we connect to an LDAP server, first try LDAPv3 (which is the preferred protocol as of now) and then fall back to LDAPv2. In case of binary attributes, we first convert them to base64, just like the openldap client does. It uses ldap_get_values_len() instead of ldap_get_values() to be able to retrieve binary attributes correctly. I defined the necessary LDAP macros in lib/ldap.c to be able to compile libcurl without the presence of libldap
2005-10-31 03:55:01 -05:00
Fresh, tommink[at]post.pl, Gisle Vanem, Nis Jorgensen, Vilmos Nebehaj
start working on 7.11.1
2004-01-22 04:40:30 -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