Re: [squid-users] Dynamic Client Bypass

Henrik Nordström wrote:

>If the the same router is used by the cache server then it will be involved
>again, and needs to have rules not to redirect the traffic again.
>
>If another router is used by the cache server, then there is no problem.
>
>You only need a single ACL in the router, telling that traffic arriving via
>the cache server is not to be redirected. The full ruleset on which sites to
>bypass the cache on is on the cache server (also acting as a router).
>
>Regards
>Henrik
>
>
>Francisco Obispo wrote:
>
>>it doesn't say anything about the router being involved in the
>>process... also, the Cisco Cache Engine will send and automatic HTTP
>>retry message, which has to be sent in this case by squid which has the
>>active conection with the client.
>>
>>I don't see an easy solution to this... except acls in the router, which
>>will lead to mantain a very very large list of sites with ip-based
>>authentication. :^/
>>
>
Yes, I understand that, but in our case, there's a single router which
has our conectivity to the outside world (a Cisco 7513), which is also
conected to a frame relay network serving many other sites which are
currently being cached.

We have one Fast Ethernet Interface dedicated to the cache server.

what about the HTTP RETRY header? any ideas?

thanks

-francisco
Received on Wed Jul 17 2002 - 14:51:56 MDT