On 5/01/2016 2:01 p.m., Alex Samad wrote: > from the logs > > # these 2 are from my laptop to alcdmz which then talks to gsdmz1, > which responds with a 504 > > Jan 05 11:55:53 2016.808 0 alcdmz1.abc.com TCP_HIT/504 4800 GET > http://wiki.squid-cache.org/wiki/squidtheme/js/niftyCorners.css - > HIER_NONE/- text/html > Jan 05 11:55:55 2016.332 0 alcdmz1.abc.com > TCP_CLIENT_REFRESH_MISS/504 4642 GET > http://wiki.squid-cache.org/wiki/squidtheme/js/niftyCorners.css - > HIER_NONE/- text/html The first request looks like the sibling 504 bug we went over earlier - I think it is caused by the revalidation being needed on the peer. The client request has required revalidation explicitly. So when the fetch reached the peer the same logic path bug occurs. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
