On Thu, Apr 18, 2002 at 12:54:51AM +0200, Henrik Nordstrom wrote:
> Brett Lymn wrote:
>
> > OK - so I put:
> >
> > cache_peer_access foo.bar allow dst_class_b
> > cache_peer_access other.bar deny dst_class_b
> > cache_peer_access yam.bar deny dst_class_b
> >
> > but now I get a TCP_MISS/503 log message in the log file... squid is
> > not trying to forward the request to the parent at all?
>
> Then you are using never_direct, and Squid could not find a functioning
> peer to send the request to..
>
Yes, that is what I thought...
> I don't see any obvious error in the above cache_peer_access rules,
> assuming the peer and acl names are correct..
>
As it turns out there is no error in the above _but_ I still had the:
cache_peer_domain foo.bar .foo.domain.com
furtuher up in my squid.conf. I commented this out and suddenly the
cache_peer_access directive appear to work. I can only guess that the
cache_peer_domain directives were overiding cache_peer_domain.
I am running Squid-2.4-PRE-STABLE if that makes a diff.
-- Brett LymnReceived on Thu Apr 18 2002 - 06:47:19 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:07:36 MST