Re: [SQU] The no_cache command is troublesome for already-cache objects

From: Robert Collins <[email protected]>
Date: Fri, 8 Dec 2000 11:12:45 +1100

Chris,
I think you are confusing the DIRECT hierarchy code and cacheability of the object.

you can have a cache hit on DIRECT, and cache misses on peer retrievals.
(i.e. if your server contacts the origin server directly, and does an IMS request, and gets Not Modified back, then you will have a
cache hit).
always_direct controls the communication path, not the cache path. Serving cache hits may or may not require communicating with an
upstream server depending on the objects age.

always_direct does work with dstdomain acls, it just has nothing to do with cacheability.

You are correct in that no_cache doesn't flush the cache of current hot or warm cache objects. Search the list for 'purge' and you
will see discussions on how to do that. That should solve your problem for existing cached objects.

Rob

----- Original Message -----
From: "Chris Conn" <cconn@abacom.com>
To: <squid-users@ircache.net>
Sent: Friday, December 08, 2000 8:59 AM
Subject: [SQU] The no_cache command is troublesome for already-cache objects

> Hello,
>
> >From the FAQ:
>
> 10.3 how do I configure Squid not to cache a specific server?
>
> acl someserver dstdomain .someserver.com
> no_cache deny someserver
>
> This works, however only of content that has not already been cached.
> In the case where cache-unfriendly sites are found _after_ they are
> cached, it seems impossible to bypass squid to go DIRECT. If I use the
> "client" program to remove objects manually, I then get the desired
> effect however it is quite tedious to remove hundreds of objects
> manually.
>
> Is there a patch to Squid 2.3-STABLE4 that would cause squid to REMOVE
> cached objects when found yet matching a no_cache ACL and serve them
> direct instead of serving from cache even when a no_cache for the domain
> has been configured?
>
> I have tried with the "always_direct" keyword too with not much success,
> but I recall that this configuration statement does not work with
> "dstdomain" ACLs.
>
> Any help would be appreciated,
>
> Chris
>
> --
> To unsubscribe, see http://www.squid-cache.org/mailing-lists.html
>
>

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html
Received on Thu Dec 07 2000 - 17:06:47 MST

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:56:53 MST