Problems with users getting old cache versions

[Kristoffer Brabrand]

We're having a problem with users getting an old cache version every now and then. Most of the times it happens in the morning, it might be something with the browsert not beeing used overnight?

What I do know for a fact is that the page looks right behind varnish, so it must be either Varnish, headers or the browser – or a combination of the ones mentioned.

Headers sent from backend to Varnish:
> Status: HTTP/1.1 200 OK
> Date: Thu, 06 Jan 2011 14:01:29 GMT
> Server: Apache/2.2.12 (Ubuntu)
> X-Powered-By: PHP/5.2.10-2ubuntu6.5
> Cache-control: max-age=600
> Connection: close
> Content-Type: text/html; charset=utf-8


Headers sent from Varnish to browser:
> Status: HTTP/1.1 200 OK
> Server: Apache/2.2.12 (Ubuntu)
> X-Powered-By: PHP/5.2.10-2ubuntu6.5
> Cache-control: max-age=600
> Content-Type: text/html; charset=utf-8
> Content-Length: 92664
> X-hash: /#www.XXXX.no#
> Date: Thu, 06 Jan 2011 13:59:45 GMT
> X-Varnish: 393208439 393133417
> Age: 528
> Via: 1.1 varnish
> Connection: close
> X-Cache: HIT
> X-Cache-hits: 158
> X-Server: Percy

I've uploaded the VCL file here: http://pastebin.com/4SyVDy70

Could it be that the browser for some reason decides it doesn't want to check for/load a new version from the host? I'm no Varnish expert, and even though I've been able to solve what's come up through the year this one is driving me mad.

Some help would be mostly appreciated!

Kind regards,
K. Brabrand
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20110106/25e2decf/attachment-0003.html>