[moved from -dev to -misc] "Manuel Amador (Rudd-O)" <[EMAIL PROTECTED]> writes: > As you might already have noted, I reported a bug on varnish caching > files indiscriminately.
This is not a bug, it is a misunderstanding. It appears you expect Varnish to act like an RFC 2616 "shared cache" whereas it is in fact a "surrogate" (see the "Edge Architecture Specification" by Oracle and Akamai, although Varnish does not yet fully implement that specification either) > My page sets a few cookies. That'd be okay and it should produce > dynamic pages, which Varnish is furnishing through my backend. The > thing is, these cookies are sent along requests for CSS and PNG and JPG > and JS files, which causes varnish to contact the backend. I don't want > that to happen (I'm happy with them being cached by Varnish 120 > seconds). > > How can I tell Varnish that requests with a response that includes ETag > (a discriminant for static files) should be forcibly cached? This is basically the same issue as in your previous email, and the answer is the same. DES -- Dag-Erling Smørgrav Senior Software Developer Linpro AS - www.linpro.no _______________________________________________ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc