Re: persistent forwarding loop

On Tue, 11 Jan 2000, Matija Grabnar wrote:

> I have a child cache (Squid-2.3Stable1) and a parent cache (Squid-2.2Stable5).
> The child cache has never_direct allow all, and the parent cache as a parent.
>
> Both caches were compiled with --enable-digest, but the child cache is
> unable to fetch the digests from the parent: every time I get
>
> 2000/01/11 10:25:46| WARNING: Forwarding loop detected for:
> GET /squid-internal-dynamic/netdb HTTP/1.0
> Host: 193.2.1.88:3128
> Via: 1.0 rzenik:3128 (Squid/2.3.STABLE1), 1.0 proxy.arnes.si:3128
> (Squid/2.2.STABLE5)
> X-Forwarded-For: unknown, 193.2.1.232
> Cache-Control: max-age=259200
> Connection: keep-alive
>
> I have checked and rechecked the configuration file for the parent and I don't
> see any lines where it could be refering to itself. I tried looking for the
> hostname as well as for the IP number, but couldn't find anything suspicious.
>
> I tried setting the parent cache as sibling, but that just made it impossible
> to fecth _anything_ (as the comment in the configuration file suggests).
> I tried removing the never_direct in the child, but that didn't help either.
>
> Could someone tell me what else I can check in the parent's or the child's
> configuration file?

One thing that can cause a forwarding loop is when your cache has
multiple hostnames. If the child cache uses a different hostname
than the parent cache's "primary" name, then it might not be
recognized as an "internal" request.

The way to fix it with 2.3 is to add other known hostnames to
the hostname_aliases option in squid.conf.

Duane W.
Received on Thu Jan 13 2000 - 14:19:48 MST