diff options
| author | Daniel Stenberg <daniel@haxx.se> | 2002-08-22 19:03:54 +0000 |
|---|---|---|
| committer | Daniel Stenberg <daniel@haxx.se> | 2002-08-22 19:03:54 +0000 |
| commit | f636c12255869039ff7874ce3b02363f327e427e (patch) | |
| tree | 198c665836840fd8154ee831d34e1ff5b979317d | |
| parent | 03e4a8214c1f5c9600e2d252150bcd7d0302c6c7 (diff) | |
bug report #588027 converted to a KNOWN BUG, as we have no intention to
correct this problem within the nearest period
| -rw-r--r-- | docs/KNOWN_BUGS | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS index c46a6153a..386712c00 100644 --- a/docs/KNOWN_BUGS +++ b/docs/KNOWN_BUGS @@ -12,6 +12,16 @@ may have been fixed since this was written! * GOPHER transfers seem broken +* 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 + ------------------------------------------------------------------------------ Q: My program blows up when I run lots of curl_easy_perform() calls on a |