True. This is how no_cache works. It only stops content from being
cached, it does not stop the cache from being used.
To change this you need to change how Squid uses the no_cache directive.
always_direct has no relation to caching, only peer selection.
Regards
Henrik Nordström
Squid Hacker
Florian Effenberger wrote:
>
> Hello,
>
> I have big trouble with Squid 2.4-STABLE2 @ Linux 2.4.10
>
> We have several groups of clients, all of them sorted into ACLs.
> Filtering with these ACLs just works fine.
>
> When I set no_cache DENY <acl> this works as well, as soon as this
> group of clients fetches content, it is being deleted out of my cache
> immediately.
>
> However, I have the following problem:
>
> If another group of clients, to which no_cache DENY does not apply,
> fetches something, I get the cached version as well.
>
> Anyone has an idea how to tell Squid that some clients should ALWAYS
> go directly, no matter if the object exists in the cache or not?
> always_direct allow <ACL> does not seem to work :o(
>
> Thanks in advance,
> Florian
Received on Thu Oct 18 2001 - 14:23:13 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:02:52 MST