Re: [squid-users] precedence of never-direct and cache_peer_access

From: Henrik Nordstrom <hno@dont-contact.us>
Date: Mon, 18 Oct 2004 11:43:26 +0200 (CEST)

On Mon, 18 Oct 2004, Rolf wrote:

> proxy sits behind firewall so origin servers are never contacted. every
> request goes via upstream servers defined by cache_peer ...
>
> "never-direct allow all" is also set.

Ok. Then for each request (where not overridden by always_direct) there
must be a alive cache_peer, or Squid will return an error.

> cache_peer_access the_3rd_proxy allow acl_domainX
>
> sufficient to ensure that domainX is retrieved via that proxy rather than the
> ones defined by cache_peer ... ?

You also need to deny it from the other peers.

cache_peer_access is just a filter on which of your defined peers is
viable to forward the request to, after cache_peer_access is the peer
selection algorithms (round-robin, ICP, digest, default, etc..) selecing
in which order the viable peers for this request will be tried.

Regards
Henrik
Received on Mon Oct 18 2004 - 03:43:30 MDT

This archive was generated by hypermail pre-2.1.9 : Mon Nov 01 2004 - 12:00:02 MST