obj.cacheable vs expires headers?

Poul-Henning Kamp phk at phk.freebsd.dk
Mon Feb 8 21:43:34 CET 2010

In message <4B708469.9070708 at gmail.com>, Luc Stroobant writes:
>Poul-Henning Kamp wrote:
>> Check your varnishlog output, it shows all headers sent/received
>> and look for what cache-control the backend gives varnish...
>The cache-control headers of the backend seem to be ok?
>(btw, the Varnish test-instance is running on my laptop, but the 
>behaviour is exactly the same as it was on the production server)

>     9 RxHeader     b Expires: Sun, 19 Nov 1978 05:00:00 GMT

This is your problem: the backend says that the object is already
expired, so obviously we cannot cache it for any amount of time.

Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

More information about the varnish-misc mailing list