Re: Looping weirdness.

Hi Alex

make a rule in the cache which deny the proxy to forward a request..
something like:

put the address of the proxies in a file..
Add the following in the squid.conf:

acl proxies "/opt/squid/etc/proxies"
cache_peer_access CACHE_A deny proxies

which means that in this case CACHE_B is not allowed to forward a
request to CACHE_A nor to itself.

Now you should be free of loops..

pascal

alex@zeelandnet.nl wrote:
>
> Hi,
>
> I've got two caches here A and B. A is the 'main' cache witch gets all the
> users requestes. B is a 'helper' cache for A.
>
> A requests cache-digests from B. The strange thing is when A requsts a
> cache-digest from B I get:
>
> 1999/06/10 14:44:47| WARNING: Forwarding loop detected for:
> GET /squid-internal-periodic/store_digest HTTP/1.0
> If-Modified-Since: Thu, 10 Jun 1999 11:39:47 GMT
> Accept: application/cache-digest
> Accept: text/html
> Host: cacheB:800
> Via: 0.0 cacheA:800 (Squid/2.2.STABLE3), 1.0 cacheB:800 (Squid/2.2.STABLE3)
> X-Forwarded-For: unknown, cacheA
> Cache-Control: max-age=1209600
> Connection: keep-alive
>
> on the B machine.
>
> So according to the docs the last host in the Via: list is the host witch
> forwarded the request. So cache B is forwaring the request to it's self?!?!
> How is this ever possible?
>
> I know I can prevent this by using acl's and stuff, but it seems more like
> a bug to me. Isn't it completely useless to forward a request to yourself?
> Should digests be forwarded anyway?
>
> cacheA has cacheB configured as a parent, cacheB A as a sibling.
>
> Thanks for any thoughts.
>
> alex.