When we receive a "bad header" we must sure not to write down the data part
authorDaniel Stenberg <daniel@haxx.se>
Fri, 11 Oct 2002 20:55:08 +0000 (20:55 +0000)
committerDaniel Stenberg <daniel@haxx.se>
Fri, 11 Oct 2002 20:55:08 +0000 (20:55 +0000)
as well, as then we write the same data twice.

lib/transfer.c

index 1de4fcc..247e402 100644 (file)
@@ -817,12 +817,12 @@ CURLcode Curl_readwrite(struct connectdata *conn,
                                        k->hbuflen);
             k->badheader = FALSE; /* taken care of now */
           }
-
-          /* This switch handles various content encodings. If there's an
-             error here, be sure to check over the almost identical code in
-             http_chunk.c. 08/29/02 jhrg */
+          else {
+            /* This switch handles various content encodings. If there's an
+               error here, be sure to check over the almost identical code in
+               http_chunk.c. 08/29/02 jhrg */
 #ifdef HAVE_LIBZ
-          switch (k->content_encoding) {
+            switch (k->content_encoding) {
             case IDENTITY:
 #endif
               /* This is the default when the server sends no
@@ -847,8 +847,9 @@ CURLcode Curl_readwrite(struct connectdata *conn,
                      "content encodings.");
               result = CURLE_BAD_CONTENT_ENCODING;
               break;
-          }
+            }
 #endif
+          }
 
           if(result)
             return result;