Keeping object in cache regardless of max-age

[Anders Daljord Morken]

On Wed, Apr 10, 2013 at 1:15 AM, Blake Crosby <blake.crosby at cbc.ca> wrote:

> Is it possible for Varnish to keep the object in cache past its TTL
> and if a future request is made for that object (which is now expired)
> that varnish will issue a If-Modified-Since (IMS) request. If the
> origin returns a 304 Not-Modified Varnish will serve the object from
> cache and reset the TTL counter?
>

Possible, well, sort of. Some work has been made on this, but it hasn't
been merged into mainline, let alone released.

See https://www.varnish-cache.org/trac/wiki/BackendConditionalRequests for
more information. The Varnish devs may have more information, but I don't
think we can expect a timeline commitment yet.

- at M
-- 
 "Sooner or later we're going to run out of things to go wrong, and
then it'll work great." - Jamie Hyneman, The Mythbusters
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20130410/ddc617c2/attachment.html>