mirror of
https://github.com/moparisthebest/curl
synced 2024-12-21 23:58:49 -05:00
numerous corrections since the 7.7 release
This commit is contained in:
parent
9a85172896
commit
bb601731ea
39
CHANGES
39
CHANGES
@ -6,6 +6,45 @@
|
||||
|
||||
History of Changes
|
||||
|
||||
Daniel (24 March 2001)
|
||||
- Colin Watson reported about a problem and brought a patch that corrected it,
|
||||
which was about the man page and lines starting with a single quote (') in a
|
||||
way that gnroff doesn't like.
|
||||
|
||||
Daniel (23 March 2001)
|
||||
- Peter Bray reported correctly that the root makefile used make instead of
|
||||
$(MAKE) for the test target.
|
||||
|
||||
- Corrected the Curl::easy perl interface to use curl_easy_setopt() and not
|
||||
curl_setopt() which was removed in 7.7!
|
||||
|
||||
- SM provided updates on three documents (MANUAL, INSTALL and FAQ).
|
||||
|
||||
- When following a Location:, libcurl would sometimes write to the URL string
|
||||
in a way it shouldn't. As the pointer is passed-in to libcurl from an
|
||||
application, we can't be allowed to write to it. The particular bug report
|
||||
from 'nk' that brought this up was because he had a read-only URL that then
|
||||
caused a libcurl crash!
|
||||
|
||||
- No longer reads HEAD responses longer than to the last header. Previously,
|
||||
curl would read the full reply if the connection was a "close" one.
|
||||
|
||||
- libcurl did re-use connections way too much. Doing "curl
|
||||
http://www.{microsoft,ibm}.com" would make it re-use the connection which
|
||||
made the second request return very odd results.
|
||||
|
||||
Daniel (22 March 2001)
|
||||
- Edin Kadribasic made me aware that curl should not re-send POST requests
|
||||
when following 302-redirects. I made 302 work like 303 which means curl uses
|
||||
GET in the following request(s).
|
||||
|
||||
- libcurl now reset the "followed-location" counter on each invoke of
|
||||
curl_easy_perform() as it otherwise would sum up all redirects on the same
|
||||
connection and thus could reach the maxredirs counter wrongly.
|
||||
|
||||
- Jim Drash suggested curl_escape() should not re-encode what already looks
|
||||
like an encoded sequence and I think that's a fair suggestion.
|
||||
|
||||
Version 7.7
|
||||
|
||||
Daniel (22 March 2001)
|
||||
|
Loading…
Reference in New Issue
Block a user