RE: [squid-users] Intentional Forwarding Loop ...

> -----Original Message-----
> From: James Hall-Kenney [mailto:James.Hall-Kenney@sytec.co.nz]
> Sent: Monday, April 09, 2001 3:35 PM
> To: Robert Collins; squid-users@squid-cache.org
> Subject: RE: [squid-users] Intentional Forwarding Loop ...
>
>
> I might be missing something but I believe that I am doing
> this. As per the
> log:
>
> 986793141.884 301 202.36.203.149 TCP_MISS/200 476 GET
> http://www.microsoft.com/business/script/globaltoolbar.js -
> DIRECT/www.microsoft.com application/x-javascript
> 986793141.995 463 202.36.203.62 TCP_MISS/200 522 GET
> http://www.microsoft.com/business/script/globaltoolbar.js -
> FIRST_UP_PARENT/localhost.dmz.dmzglobal.net application/x-javascript
>
> 202.36.203.62 is the client. 202.36.203.149 is the squid
> server. It seems
> to log the first completed transaction first??? ie the GET after the
> viruswall.
>
> The acl is:
> # this ACL allows traffic that comes back from the viruswall
> to go the net
> acl thishost src 202.36.203.149/255.255.255.255
> always_direct allow thishost
> http_access allow thishost
>
> Am I missing something? My thort was that as the visible
> name of this proxy
> was already in the header request, it was seeing this as a
> forwarding loop
> ...
>
> Regards
>
> James
>

Hmm, I'm not familiar with the forward loop detection code.

You do have another option:
create a second squid.conf file with the null store filesystem,
listening on a different port and use this as the interscan parent. This
would give you the desired network efficiency w/o wasting disk space.

Rob
Received on Sun Apr 08 2001 - 23:58:58 MDT