HTTP 304 response with Content-Length: header

This commit is contained in:
Daniel Stenberg 2005-04-10 22:56:46 +00:00
parent bee198def5
commit 37f7362aca
2 changed files with 9 additions and 2 deletions

View File

@ -6,6 +6,11 @@
Changelog
Daniel (8 April 2005)
- Cory Nelson reported a problem with a HTTP server that responded with a 304
response containing an "illegal" Content-Length: header, which was not
properly ignored by libcurl. Now it is. Test case 249 verifies.
Daniel (7 April 2005)
- Added ability to build and run with GnuTLS as an alternative to OpenSSL for
the secure layer. configure --with-gnutls enables with. Note that the

View File

@ -5,7 +5,7 @@ Curl and libcurl 7.13.3
Available command line options: 106
Available curl_easy_setopt() options: 122
Number of public functions in libcurl: 46
Amount of public web site mirrors: 20
Amount of public web site mirrors: 21
Number of known libcurl bindings: 31
This release includes the following changes:
@ -15,15 +15,17 @@ This release includes the following changes:
This release includes the following bugfixes:
o HTTP 304 response with Content-Length: header
o time-conditioned FTP uploads
Other curl-related news since the previous public release:
o http://curl.mirroring.de/ is a new german curl mirror
o pycurl 7.13.2: http://pycurl.sf.net/
This release would not have looked like this without help, code, reports and
advice from friends like these:
Christophe Legry,Cory Nelson
Thanks! (and sorry if I forgot to mention someone)