From a942c2065a2f055ca9358b9e378a6abaffaabfe5 Mon Sep 17 00:00:00 2001 From: Amos Jeffries Date: Sat, 12 Apr 2008 08:03:26 -0600 Subject: [PATCH] Author: Henrik Nordstrom Fallback on transparent interception mode even if the connection didn't seem to be transparently intercepted Needed to deal properly with situations where connections to the local host is intercepted, or when people NAT outside the Squid server but still compile Squid with support for the NAT/interception method availabe on the host OS.. --- src/client_side.cc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/client_side.cc b/src/client_side.cc index 06c9bb42ef..2916e7853e 100644 --- a/src/client_side.cc +++ b/src/client_side.cc @@ -1963,6 +1963,9 @@ parseHttpRequest(ConnStateData::Pointer & conn, HttpParser *hp, method_t * metho /* prepend our name & port */ http->uri = xstrdup(internalLocalUri(NULL, url)); http->flags.accel = 1; + } else if (conn->port->transparent) { + // Fallback on transparent if enabled, useful for "self" requests + prepareTransparentURL(conn, http, url, req_hdr); } if (!http->uri) { -- 2.47.2