Re: hierarchy_stoplist & cache digests

I would also say that it shows misfeature of digest (and ICP) peerings.
I think that it can be generally assumed that sibling hits for other
than status 200 objects is undesirable, and of limited use in parent
peerings.

Perhaps only status 200 objects should be included in digests?

See my related message (and patch) on ICP peerings and Squid 2.1.X
forwarding loops on non-200 responses.

/Henrik

Duane Wessels wrote:

> >However one of our neighbours has a cache digest with a hit for the page -
> >basicly an error message saying the neighbour can not access.
> >
> >Despite the hierarchy, we are getting cache digest hits:
> >
> >926522637.611 224 134.83.66.171 TCP_MISS/200 869 GET
> >http://infotrac.galegrou
> >p.com/itweb/bu_itc - CACHE_DIGEST_HIT/brunel0.sites.wwwcache.ja.net text/html
> >
> >This is under Squid 2.1p2 - do we need always_direct statements as well?
>
> No, this is a bug.
Received on Tue Jul 29 2003 - 13:15:58 MDT