On fre, 2008-07-11 at 03:57 -0700, John Doe wrote:
> Works fine for a while... until the digests are exchanged.
> As expected, my logs are full of forwarding loops detected.
Hmm... you SHOULD NOT see loops unless you are using the allow-miss
cache_peer option, as by default Squid adds a "Cache-Control:
only-if-cached" control to requests sent to siblings.
Are you playing games with the Cache-Control header somewhere?
> 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...
That should defenitely help.
What is said in access.log?
Regards
Henrik
This archive was generated by hypermail 2.2.0 : Fri Jul 11 2008 - 12:00:03 MDT