On Mon, Dec 13, 2010 at 12:08 PM, James A. Robinson < [email protected]> wrote:
> On Mon, Dec 13, 2010 at 08:55, Jacob Elder <[email protected]> wrote: > > Just posting this so it will make it into the mailing list archives, and > > hopefully spark a discussion: > > The default Varnish config does not honor "no-cache" in Cache-control > > headers. It is my personal opinion that it should, but it's easy enough > to > > add this behavior if desired. > > sub vcl_fetch { > > if (beresp.http.cache-control ~ "no-cache") { > > return(pass); > > } > > } > > I think it really depends on your application. As someone who deals > with publications that change rarely (new content comes in frequently, > but rarely changes), we have to deal with bots that crawl the site and > specify no-cache -- it doesn't make sense to honor that request if we > know the data hasn't actually changed. > > > Jim > You are right but I should have been more clear. I believe that Varnish should honor no-cache from backends but not necessarily from clients. -- Jacob Elder @jelder (646) 535-3379
_______________________________________________ varnish-misc mailing list [email protected] http://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
