I believe you should upgrade to 2.0.5 (or scan Varnish ticket #529 for a patch) which retains this and other headers in a 304 response. -- Ken
On Nov 18, 2009, at 5:05 AM, Lars Jørgensen wrote: > Hi, > > Another one that I'm trying to work out at the moment. I have enabled > mod_expires in Apache and set a 24 hour expiration on css. When I request a > page directly from the backend, a CSS object looks like this: > > Date: Wed, 18 Nov 2009 12:57:50 GMT > Server: Apache/2.2.3 (Debian) PHP/5.2.0-8+etch13 > Connection: Keep-Alive > Keep-Alive: timeout=15 > Etag: "da8e2c-e663-6c305b40" > Expires: Thu, 19 Nov 2009 12:57:50 GMT > Cache-Control: max-age=86400 > > The same object through Varnish: > > Date: Wed, 18 Nov 2009 12:56:24 GMT > Via: 1.1 varnish > X-Varnish: 71655288 > Last-Modified: Mon, 22 Jun 2009 10:34:45 GMT > Connection: keep-alive > > I do get "304 Not Modified" on the object, but shouldn't I get the Expires > and Cache-Control headers too? > > > -- > Lars > > > > > _______________________________________________ > varnish-misc mailing list > [email protected] > http://projects.linpro.no/mailman/listinfo/varnish-misc _______________________________________________ varnish-misc mailing list [email protected] http://projects.linpro.no/mailman/listinfo/varnish-misc
