On 2016-12-29 16:03, Ivan Larionov wrote:
Hello! I'm trying to setup multiple squids as siblings with a parent which is not even a squid. But I'm getting following message in logs: temporary disabling (Bad Gateway) digest from 172.22.15.88 temporary disabling (Bad Gateway) digest from … Squid 3.5.23, compiled with "--enable-cache-digests". For parent I'm setting no-digest, but I'd like to get digests between siblings. However, it doesn't work and I probably found a reason after reading debug logs: This is how squid does store_digest request from a sibling peer: GET http://172.22.15.88:3128/squid-internal-periodic/store_digest [1] HTTP/1.1 Accept: application/cache-digest Accept: text/html X-Forwarded-For: unknown Host: 172.22.15.88:3128 [2] Cache-Control: max-age=259200 Connection: keep-alive Response (if I execute this request manually from telnet): HTTP/1.1 502 Bad Gateway … This request has been forwarded to a parent and parent returned 502!
Are you sure about that forwarding? Its not being generated by the sibling?
Now if I manually do the same request with a relative URL: GET /squid-internal-periodic/store_digest HTTP/1.1 … Response: HTTP/1.1 200 Cache Digest OK … My setup: Multiple squids as siblings, one parent (not a squid). Peers configuration: # Other squids cache_peer 172.22.15.88 sibling 3128 4827 htcp cache_peer … sibling 3128 4827 htcp acl siblings src 172.22.15.88/32 [3] acl siblings src …/32 miss_access deny siblings # Parent cache_peer 127.0.0.1 parent 18070 0 no-query no-digest name=NAME cache_peer_access NAME deny some_acl Anyone else seen similar issue? Do you have an example of working configuration with multiple siblings and enabled digests?
The default config usually just works. Do you have "global_internal_static off" in your squid.conf? Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
