bug report #588027 converted to a KNOWN BUG, as we have no intention to
correct this problem within the nearest period
This commit is contained in:
Родитель
03e4a8214c
Коммит
f636c12255
|
@ -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
|
||||
|
|
Загрузка…
Ссылка в новой задаче