On Tue, Apr 16, 2002 at 09:42:47AM +0200, Henrik Nordstrom wrote:
>
> See cache_peer_access, same thing as cache_peer_domain but much more
> flexible in terms on what you control the peer usage.
>
Hmmm I had tried that before but I could not get that to work, I have
tried again but it still seems not to be selecting the correct
parent. What I have is something like:
cache_peer_domain foo.bar .some.domain.com
cache_peer_domain bar.bar .another.domain.org
cache_peer_domain catch.all !.some.domain.com !.another.domain.org
....
acl dst_class_b dst 10.10.0.0/255.255.0.0
cache_peer_access foo.bar allow dst_class_b
<lots of other http_access stuff follows>
When I do this it seems like any requests for an IP address on the
class-b are still going to the default parent (catch.all) - I have
tried adding a cache_peer_access deny just after the allow to deny any
other destination but that has made no difference.
-- Brett LymnReceived on Tue Apr 16 2002 - 06:59:19 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:07:35 MST