Re: peering

From: Bruce Campbell <>
Date: Tue, 5 May 1998 15:50:07 +1000 (EST)

On Tue, 5 May 1998, Antony wrote:

> We've set up a new peering link where the peer is allowed to access our
> cache as a sibling for cache hits, but is not allowed to pull through out
> cache.
> I am seeing this...
> 894341279.884 1393 TCP_REFRESH_HIT/200 619 GET
> -
> PARENT_HIT/ image/gif

*shrug* if you are worried about it, set up an acl like:

acl apic src

and restrict it from going to CCA:

cache_host_acl !apic

> Which to me looks like they are able to pull through our cache (thus costing
> us money). Am I right or wrong on this point?

urm... sorta. I read it as your proxy already had that url in its cache,
then the apic proxy requested a refresh which your proxy obliged via CCA.
Looks like they can refresh through your cache (probably wrong on this
point ;) )

> We have other peers, everyone is configured exactly the same, yet this new
> link is the only one showing up like this.
> Any advice would be appreciated. We are running squid-1.1.20

And they are (*clickety-click*) running 1.1.10 - could be an
incompatibility thing.

Cheers ;)


K'nurdic Wrangler.
Received on Mon May 04 1998 - 22:48:06 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:40:05 MST