From 72b1144b8c1844ec81d5f5b73eb9b2a088377fec Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Wed, 7 Apr 2004 14:27:54 +0000 Subject: getting only a 100 Continue response and nothing else, when talking HTTP, is now treated as an error by libcurl --- docs/KNOWN_BUGS | 7 ------- 1 file changed, 7 deletions(-) (limited to 'docs') diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS index 6f60d4022..7726b225c 100644 --- a/docs/KNOWN_BUGS +++ b/docs/KNOWN_BUGS @@ -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: -- cgit v1.2.3