Re: Some problems with Squid 2.0 PATCH2

Martynas Buozis wrote:

> Yes. It is so. I am using squid as a proxy on this request. Older
> squid versions after geting such proxy request took data from
> accelerated httpd.

Sort of.

The request path was:
  Client or peer cache
    -> Squid as a proxy
       -> Squid as a accelerator
          -> origin server.

The difference is that older versions of Squid had a less strict loop
detection that only gave a warning on request paths like this. This
has changed in recent Squid versions to deny the request since a lot
of people had the problem that Squid infinitely asked itself on some
kinds of requests when acceleration is enabled.

> I can't see any problems in such configuration. If I am wrong, then
> what idea is of that accelerated httpd if I can't make such requests ?

You can, but you need to take special care if you are using the
accelerator as a proxy to stop the proxy from using itself when
requesting objects from the accelerated host.

> But is this normal solution? Why this feature is working on older squid
> versions without any problems?

See above.

> If there will be any fixes?

Perhaps, if a reasonable way to do it could be found.

---
Henrik Nordström
Spare time Squid hacker