Re: [squid-users] Forwarding loops...

John Doe wrote:
> Hi,
>
> still using my 4 siblings in proxy-only.
> Works fine for a while... until the digests are exchanged.
> As expected, my logs are full of forwarding loops detected.
>
> 2008/07/11 10:48:32| WARNING: Forwarding loop detected for:
> Client: 192.168.17.11 http_port: 192.168.17.11:8000
> GET http://192.168.16.23/img/taiwan.gif HTTP/1.0
> Pragma: no-cache
> User-Agent: Wget/1.10.2 (Red Hat modified)
> Accept: */*
> Host: 192.168.16.23
> Via: 1.0 Squid3:8000 (squid), 1.0 Squid1:8000 (squid), 1.0 Squid4:8000 (squid)
> X-Forwarded-For: 192.168.17.13, 192.168.17.11, 192.168.17.14
> Cache-Control: max-age=864000
> Proxy-Connection: keep-alive
>
> The problem is, since the siblings are in 'proxy-only', they do not cache the looped objects and constantly asks their apache for it.
> The next digests exchanges will fix the current loops, but will create new loops.
> To solve this, I tried to prevent a squid from querying a sibling on behalf of another sibling:
>
> example of squid1.conf:
> cache_peer 192.168.17.12 sibling 8000 3130 proxy-only name=squid2
> cache_peer 192.168.17.13 sibling 8000 3130 proxy-only name=squid3
> cache_peer 192.168.17.14 sibling 8000 3130 proxy-only name=squid4
>
> acl from_squids src 192.168.17.12
> acl from_squids src 192.168.17.13
> acl from_squids src 192.168.17.14
>
> cache_peer_access squid2 deny from_squids
> cache_peer_access squid3 deny from_squids
> cache_peer_access squid4 deny from_squids
>
> But it is not helping...
> Any idea?

Are you not configuring each squid to prefer its parent for that parents
traffic?

for example; squid1 has:

   cache_peer apache1 parent ...

   acl for_my_apache dstdomain .example.com

   cache_peer_access apache1 allow for_my_apache
   cache_peer_access squid2 deny for_my_apache
   cache_peer_access squid3 deny for_my_apache
   cache_peer_access squid4 deny for_my_apache

Amos

-- 
Please use Squid 2.7.STABLE3 or 3.0.STABLE7