> > 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? I don't have use allow-miss. But I do have: header_access Cache-Control deny all header_replace Cache-Control max-age=864000 I will try without it... > > 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? If I ask squid2 for a looping object: squid2 access.log: 1215783827.918 1 192.168.17.12 TCP_MISS/200 7188 GET http://192.168.16.23/img/spain.gif - FIRST_UP_PARENT/apache image/gif 1215783827.919 2 192.168.17.12 TCP_MISS/200 7233 GET http://192.168.16.23/img/spain.gif - CD_SIBLING_HIT/squid3 image/gif squid3 access.log: 1215783827.918 8 192.168.17.13 TCP_MISS/200 7213 GET http://192.168.16.23/img/spain.gif - CD_SIBLING_HIT/squid2 image/gif Thx, JD
