Re:Varnish 4.0.2 released
by phkamp on Thursday October 09, 2014 @09:54AM
(#8432318)
That sounds like a "hit-for-pass" scenario: Something from your backend told Varnish "Don't cache this" and varnish stopped doing so.
[ Parent
| on HN ]
This. The thing to remember is that you always have to set beresp.ttl in vcl_fetch in a hit-for-pass situation. Varnish caches the decision to hit-for-pass (or lookup or whatever), so if you do a hit-for-pass and your TTL is 1 hour, Varnish will hit-for-pass that cache key for the next hour without running your VCL logic again.
Re:Varnish 4.0.2 released
by imaginenore on Thursday October 09, 2014 @11:43AM
(#8433052)
Except we didn't have that. This was 99.9% content pages dynamically generated and nearly static. They all had roughly the same headers that haven't changed really, and they were not even aware of Varnish.
Response headers is the first thing we checked, there are only a few of them that affect Varnish:
Are you sure it wasn't an issue with cache evictions?
Re:Varnish 4.0.2 released
by imaginenore on Thursday October 09, 2014 @05:26PM
(#8435096)
All pages at the same exact time?