]> git.ipfire.org Git - thirdparty/squid.git/commitdiff
Bug 3173: Assertion bodyPipe!=NULL on SslBump CONNECT response writing failure
authorAlex Rousskov <rousskov@measurement-factory.com>
Wed, 30 Mar 2011 11:53:48 +0000 (05:53 -0600)
committerAmos Jeffries <squid3@treenet.co.nz>
Wed, 30 Mar 2011 11:53:48 +0000 (05:53 -0600)
Do not call ConnStateData::startClosing() when we fail to write our CONNECT
response while bumping a connection. startClosing() can only be used when we
handle response bodies. Just close the connection, in hope that the connection
close handler kicks in and cleans up.

src/client_side_request.cc

index a0034d9c5696b880a0450dc9295bec8121f3c350..aee8a0cd7799f8f23537c3e0841fca4386ec7b88 100644 (file)
@@ -1178,7 +1178,8 @@ ClientHttpRequest::sslBumpEstablish(comm_err_t errflag)
         return;
 
     if (errflag) {
-        getConn()->startClosing("CONNECT response failure in SslBump");
+        debugs(85, 3, HERE << "CONNECT response failure in SslBump: " << errflag);
+        comm_close(getConn()->fd);
         return;
     }