Re: squid 2.2 stable 4 as both proxy and accelerator

Don Rolph wrote:
>
> I have been using Squid 1.14 very nicely as a caching proxy and an
> acceleerator. I am trying to migrate to Squid 2.2 stable 4 for the same
> purpose. Looks like it works nicely as a proxy, or as an accelerator,
> but if I have a client which uses it as the proxy setting and uses it as
> an accelerator, I am getting access denied.

This is a known issue. In fact it has never worked correcly. The flaw is
in how Squid detects the requests to "accelerate". Why the error is only
detected when using Squid-2.X is because it has built-in request loop
detection that triggers when it fetches objects from itself. Squid-1.X
happily fetched objects from itself and is why it seemed to work
correctly when used as both an proxy and accelerator at the same time.

To work around the problem you can use a redirector which rewrites the
proxied requests to the accelerated servers, or configure the browsers
not to use the proxy for the accelerated servers (the no-proxy for
setting in the browsers proxy settings dialogue)

A third possibility is to use split name resolution, so that when Squid
looks up the official server name the address of the backend server is
returned. Such a setup can easily be acheived if you have a split DNS
setup with different DNS:es for internal and external use.

--
Henrik Nordstrom
Squid hacker