Bug #520: performance problem while executing the HEAD command to IIS and

certain other web servers

Caused by a malformed HTTP reply without the terminating line after the
headers. In such case we MUST NOT keep the client connection persistent
as our reply is also malformed.

diff --git a/src/client_side_reply.cc b/src/client_side_reply.cc
index 46bb0146f4591492541532769992b5e358e5f29f..520073fc9c3af33c7c63a2afbd937fcc67c1279e 100644 (file)
--- a/src/client_side_reply.cc
+++ b/src/client_side_reply.cc
@@ -1,6 +1,6 @@
 
 /*
- * $Id: client_side_reply.cc,v 1.36 2003/02/05 10:36:49 robertc Exp $
+ * $Id: client_side_reply.cc,v 1.37 2003/02/08 15:23:53 hno Exp $
  *
  * DEBUG: section 88    Client-side Reply Routines
  * AUTHOR: Robert Collins (Originally Duane Wessels in client_side.c)
@@ -1960,6 +1960,11 @@ clientReplyContext::sendMoreData (StoreIOBuffer result)
            debug (88,0)("Broken head response - probably phttpd/0.99.72\n");
            http->flags.done_copying = 1;
            flags.complete = 1;
+           /*
+            * And as this is a malformed HTTP reply we cannot keep
+            * the connection persistent
+            */
+           request->flags.proxy_keepalive = 0;
            
            StoreIOBuffer tempBuffer;
            assert(body_buf && body_size);