On tor, 2007-11-15 at 09:37 +0900, Adrian Chadd wrote: > G'day, > > I'd like to propose a Squid modification - to cache "dynamic" content > thats playing "good".
Yes, it's as simple as removing the cache lines from the default suggested config and making sure your refresh_pattern rules is reasonable. The actual default is none. The reason we block query URls is just RFC compliance in case someone uses refresh_pattern with a min age > 0, and legacy from those lines always been there.. If addressing this I think it's better done in refresh_pattern than no_cache. Additionally refresh_pattern is in serious need of a cleanup as it's been too heavily overloaded (and more is coming..). What the RFC says in 13.9 Side Effects of GET and HEAD: caches MUST NOT treat responses to such URIs as fresh unless the server provides an explicit expiration time. This specifically means that responses from HTTP/1.0 servers for such URIs SHOULD NOT be taken from a cache. Note: Explicit expiry time is Expires or Cache-Control max-age/s-maxage. Last-Modified is not. But I'd argue that the fact that last-modified based heuristics is not allowed is just an oversight and not intentional. Regards Henrik
signature.asc
Description: This is a digitally signed message part
