From 0dbf0886724284076d37d946f7fce854cb6f8f1c Mon Sep 17 00:00:00 2001 From: Amos Jeffries Date: Wed, 9 Sep 2015 09:32:08 -0700 Subject: [PATCH] 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. --- src/tunnel.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/tunnel.cc b/src/tunnel.cc index 5684e10c1f..c75ac6f89e 100644 --- a/src/tunnel.cc +++ b/src/tunnel.cc @@ -1099,8 +1099,8 @@ tunnelRelayConnectRequest(const Comm::ConnectionPointer &srv, void *data) packerClean(&p); 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, -- 2.47.2