Re: [squid-users] dst ACL element with no_cache ACL operator

Already done in Squid-2.4.

Path for earlier Squid releases are available from
http://squid.sourceforge.net/hno/ somewhere.. (probably the
"Development" section)

In earlier Squid releases using dst or other ACL types which might
require an exernal lookup in no_cache is unreliable. If an external DNS
lookup (or whatever) is required then the ACL will temporarily give a
false reading because Squid does not wait for the lookup to complete.

--
Henrik Nordstrom
Squid hacker
Jamie Norrish wrote:
> 
> Hi,
> 
> I've read in the archives that the dst ACL element is not supported by
> the no_cache operator. While I've observed this to indeed be the case,
> I've also seen in my cache.log with a high level of debugging that Squid
> is checking the dst ACL list for that operator, and coming up with
> appropriate matches. My question then is this: why, if it does the
> checking and makes a match, doesn't it then obey the no_cache operator?
> Is it just that the  logs show the checking regardless of the success or
> otherwise of their use by a particular operator?
> 
> Are there any plans to support dst elements for this operator?
> 
> Jamie