Commit 0c823a89 authored by Nils Goroll's avatar Nils Goroll

an attempt to clarify req.grace/req.ttl

parent 2cb5e532
...@@ -49,11 +49,13 @@ VCL variables ...@@ -49,11 +49,13 @@ VCL variables
since there are use cases that cannot be solved without it. Similarly, since there are use cases that cannot be solved without it. Similarly,
``req.ttl`` used to be deprecated and is now fully supported again. ``req.ttl`` used to be deprecated and is now fully supported again.
``req.ttl`` and ``req.grace`` set upper bounds on the TTL and grace ``req.ttl`` and ``req.grace`` limit the ttl and grace times that are
times that are permitted for the current request -- if these variables permitted for the current request. If ``req.ttl`` is set, it requires
are set and the TTL/grace of a cache object is longer than their cache objects to have that minimum remaining ttl to be considered
settings, then a new response is fetched from the backend, despite the fresh. Likewise, ``req.grace`` sets an upper bound on the time an
presence of an otherwise fresh cache object. object has spent in grace to be considered eligible for grace mode
(which is to deliver this object and fetch a fresh copy in the
background).
A common application is to set shorter TTLs when the backend is known A common application is to set shorter TTLs when the backend is known
to be healthy, so that responses are fresher when all is well. But if to be healthy, so that responses are fresher when all is well. But if
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment