no_cache

 < Day Day Up > 

no_cache

no_cache is a sequence of access control rules (see Section 6.2) that specify responses that must not be cached by Squid. Of course, Squid has some hardcoded rules for responses that must not be cached according to the HTTP RFC. The no_cache rules are in addition to those.

The no_cache syntax is a little tricky. You must use deny for rules where the response must not be cached. Consider this example:

 acl GoodStuff url_regex /foo/bar/ acl BadStuff url_regex /bar/ no_cache allow GoodStuff no_cache deny BadStuff 

Here, a URL containing /foo/bar/ may be cached, but any other URL containing only /bar/ isn't cached. The meaning of the allow and deny might be the opposite of what you expect. Just remember that deny carries the same negative connotation as "not caching" something.

Syntax

 no_cache allowdeny [!]   ACLname   ... 

Default

No default

Example

 acl LocalServers dst 192.168.8.0/24 no_cache deny LocalServers 

Related

always_direct , never_direct , http_access

 < Day Day Up > 


Squid
Squid: The Definitive Guide
ISBN: 0596001622
EAN: 2147483647
Year: 2004
Pages: 401
Authors: Duane Wessels

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net