From: Amos Jeffries <squid3@treenet.co.nz>
Date: Wed, 2 Sep 2015 14:17:07 +0000 (-0700)
Subject: Fix CONNECT request debugging 11,2 traces
X-Git-Tag: SQUID_4_0_1~75
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=533839e0fc067f48a3db328ccd993b921a085d4b;p=thirdparty%2Fsquid.git

Fix CONNECT request debugging 11,2 traces

Using the MemBuf::buf directly is not great, but it does have a properly
terminated c-string in this instance. We cannot use Raw() interface
because that is for output at DBG_DATA levels and will only display the
buffer name as if that was the raw traffic bytes at 11,2.
Which negates the entire purpose of this 11,2 output.
---

diff --git a/src/tunnel.cc b/src/tunnel.cc
index dbb8904079..3723ef9f4f 100644
--- a/src/tunnel.cc
+++ b/src/tunnel.cc
@@ -1110,8 +1110,8 @@ tunnelRelayConnectRequest(const Comm::ConnectionPointer &srv, void *data)
     hdr_out.clean();
     mb.append("\r\n", 2);
 
-    debugs(11, 2, "Tunnel Server REQUEST: " << tunnelState->server.conn << ":\n----------\n" <<
-           Raw("tunnelRelayConnectRequest", mb.content(), mb.contentSize()) << "\n----------");
+    debugs(11, 2, "Tunnel Server REQUEST: " << tunnelState->server.conn <<
+           ":\n----------\n" << mb.buf << "\n----------");
 
     AsyncCall::Pointer writeCall = commCbCall(5,5, "tunnelConnectReqWriteDone",
                                    CommIoCbPtrFun(tunnelConnectReqWriteDone,