aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2015-08-24 12:56:20 +0200
committerDaniel Stenberg <daniel@haxx.se>2015-08-24 12:56:20 +0200
commite7d171da6bf33fe360b4feaa0d12ea5c23855063 (patch)
treea8ab849d3c3dfed2192b8f6cc30cd54cefbc35bd /docs
parent874413b3e1f9837fbe66e08341170eb2e949b395 (diff)
KNOWN_BUGS: #2, not reading a HEAD response-body is not a bug
... since HTTP is forbidden to return any such.
Diffstat (limited to 'docs')
-rw-r--r--docs/KNOWN_BUGS10
1 files changed, 0 insertions, 10 deletions
diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index 0c0be92b6..4b869ec76 100644
--- a/docs/KNOWN_BUGS
+++ b/docs/KNOWN_BUGS
@@ -235,13 +235,3 @@ may have been fixed since this was written!
it seems HTTP servers send the *uncompressed* length in that header and
libcurl thinks of it as the *compressed* length. Some explanations are here:
http://curl.haxx.se/mail/lib-2003-06/0146.html
-
-2. If a HTTP server responds to a HEAD request and includes a body (thus
- violating the RFC2616), curl won't wait to read the response but just stop
- reading and return back. If a second request (let's assume a GET) is then
- immediately made to the same server again, the connection will be re-used
- fine of course, and the second request will be sent off but when the
- response is to get read, the previous response-body is what curl will read
- and havoc is what happens.
- More details on this is found in this libcurl mailing list thread:
- http://curl.haxx.se/mail/lib-2002-08/0000.html