From 3f458fc6506f5f84fa6fb53292711c007e11726d Mon Sep 17 00:00:00 2001
From: Daniel Stenberg <daniel@haxx.se>
Date: Fri, 17 Oct 2003 11:36:41 +0000
Subject: [PATCH] The 100-continue and no-more-response bug

---
 docs/KNOWN_BUGS | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index 16c7d8b57f..b9f8454f46 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:
-- 
GitLab