Re: peering

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 203.22.101.5 TCP_REFRESH_HIT/200 619 GET
> http://www.colorado.edu/images/nav-info.gif -
> PARENT_HIT/proxy2.syd.connect.com.au image/gif

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

acl apic src 203.22.101.0/24

and restrict it from going to CCA:

cache_host_acl proxy2.syd.connect.com.au !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 ;)

--==--
Bruce.

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