Re: [squid-users] using round-robin cache_peers and another cache_peer together

On 08/12/10 21:58, Ralf.Golfels_at_renesas.com wrote:
>
> Dear all,
>
> as describe we like to use a round-robin environment with two cache_peers
> and a third cache_peer to which some domains should be directed.
>
> Squid version is Squid Cache (version 3.1.6)...
>
> cache_peer config:
>
>
> cache_peer x.x.x.x parent 3128 0 round-robin no-query no-digest
> cache_peer y.y.y.y parent 3128 0 round-robin no-query no-digest
>
> and in the acl section:
>
> acl POST_CONNECT method POST CONNECT
> cache_peer z.z.z.z parent 80 0 proxy-only
>
> acl POST_CONNECT method POST CONNECT
> cache_peer_domain z.z.z.z sample.com
> cache_peer_domain z.z.z.z sample1.com
> cache_peer_domain z.z.z.z sample2.com
> acl 1st dstdomain sample.com sample1.com sample2.com
>
>
> if we are using this conf all redirects to sample.com are ignored. if we
> reconfigure the config to use only x.x.x.x parent without round-robin the
> redirects to sample.com via z.z.z.z cache_peer are working.
>
> Any ideas to solve it?
>
> Many thanks and best regards
>

Order is important.

either:
   Place cache_peer z.z.z.z ... first.
OR
   configure explicit access controls:
     cache_peer_access x.x.x.x deny 1st
     cache_peer_access y.y.y.y deny 1st
     cache_peer_access z.z.z.z allow 1st
(the cache_peer_domain can then be removed)

z.z.z.z peer also appears to possibly be lacking the "originserver" flag.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.9
   Beta testers wanted for 3.2.0.3