aboutsummaryrefslogtreecommitdiff
path: root/docs/KNOWN_BUGS
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2003-10-17 11:36:41 +0000
committerDaniel Stenberg <daniel@haxx.se>2003-10-17 11:36:41 +0000
commit3f458fc6506f5f84fa6fb53292711c007e11726d (patch)
treed457b3f5a9557cc47e888d23a74e92b6eadea78e /docs/KNOWN_BUGS
parent9935d33b8e63bc1772e1975ad66475375672b34b (diff)
The 100-continue and no-more-response bug
Diffstat (limited to 'docs/KNOWN_BUGS')
-rw-r--r--docs/KNOWN_BUGS7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index 16c7d8b57..b9f8454f4 100644
--- a/docs/KNOWN_BUGS
+++ b/docs/KNOWN_BUGS
@@ -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: