Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
5e2804f2
Commit
5e2804f2
authored
Sep 10, 2018
by
Nils Goroll
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
release docs: req.grace/req.ttl wording
parent
7a0f2cf7
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
upgrading-6.1.rst
doc/sphinx/whats-new/upgrading-6.1.rst
+4
-4
No files found.
doc/sphinx/whats-new/upgrading-6.1.rst
View file @
5e2804f2
...
...
@@ -56,15 +56,15 @@ VCL variables
``req.ttl``, ``req.grace`` and keep
-----------------------------------
``req.
ttl`` had been previously listed as deprecated, but it is now
fully supported, since there are use cases that cannot be solved
without it
.
``req.
grace`` had been previously removed, but was now reintroduced,
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`` and ``req.grace`` set upper bounds on the TTL and grace
times that are permitted for the current request -- if these variables
are set and the TTL/grace of a cache object is longer than their
settings, then a new response is fetched from the backend, despite the
presence of
the response in the cache
.
presence of
an otherwise fresh cache object
.
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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment