[squid-users] squid sibling peers and digest requests

Ivan Larionov xeron.oskom at gmail.com
Thu Dec 29 03:03:41 UTC 2016


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
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:

Accept: application/cache-digest
Accept: text/html
X-Forwarded-For: unknown
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!

Now if I manually do the same request with a relative URL:

GET /squid-internal-periodic/store_digest HTTP/1.1


HTTP/1.1 200 Cache Digest OK

My setup:

Multiple squids as siblings, one parent (not a squid).

Peers configuration:

# Other squids
cache_peer sibling 3128 4827 htcp
cache_peer … sibling 3128 4827 htcp
acl siblings src
acl siblings src …/32
miss_access deny siblings

# Parent
cache_peer 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?

With best regards, Ivan Larionov.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20161228/985c6e35/attachment-0001.html>

More information about the squid-users mailing list