no_cache blocks content from getting cached. Nothing more.
As discussed several times lately, no_cache does NOT block cached content
from being cache hits. Because of this you cannot base no_cache on the user
making the request, only on the destination or requested content.
If any other behaviour of no_cache is wanted, such as the option of bypass
the cache for certain users then coding is required.
Regards
Henrik Nordstr�m
Squid Hacker
On Friday 09 November 2001 11.34, Klavs Klavsen wrote:
> b,
>
> Nice to know I'm not alone in this :-)
>
> I'm not sure, but I think the no_cache tag means, that it caches the object
> - but refreshes it everytime - and if this is so,
Received on Fri Nov 09 2001 - 07:09:57 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:04:00 MST