Commit 3f458fc6 authored by Daniel Stenberg's avatar Daniel Stenberg
Browse files

The 100-continue and no-more-response bug

parent 9935d33b
Loading
Loading
Loading
Loading
+7 −0
Original line number Diff line number Diff line
@@ -3,6 +3,13 @@ join in and help us correct one or more of these! Also be sure to check the
changelog of the current development status, as one or more of these problems
may have been fixed since this was written!

* 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: