mirror of
https://github.com/curl/curl.git
synced 2026-08-25 11:13:32 +03:00
getting only a 100 Continue response and nothing else, when talking HTTP,
is now treated as an error by libcurl
This commit is contained in:
parent
348fe0e210
commit
72b1144b8c
9 changed files with 102 additions and 38 deletions
|
|
@ -23,13 +23,6 @@ may have been fixed since this was written!
|
|||
indicate that the user wants to reach the root dir (this exception SHALL
|
||||
remain even when this bug is fixed).
|
||||
|
||||
* 1) libcurl does a POST
|
||||
2) receives a 100-continue
|
||||
3) sends away the POST
|
||||
Now, if nothing else is returned from the server, libcurl MUST return
|
||||
CURLE_GOT_NOTHING, but it seems it returns CURLE_OK as it seems to count
|
||||
the 100-continue reply as a good enough reply.
|
||||
|
||||
* libcurl doesn't treat the content-length of compressed data properly, as
|
||||
it seems HTTP servers send the *uncompressed* length in that header and
|
||||
libcurl thinks of it as the *compressed* lenght. Some explanations are here:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue