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
91047a9e
Commit
91047a9e
authored
Mar 12, 2017
by
Geoff Simmons
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Grammar OCD
parent
65c6290b
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
8 deletions
+9
-8
upgrading-5.1.rst
doc/sphinx/whats-new/upgrading-5.1.rst
+9
-8
No files found.
doc/sphinx/whats-new/upgrading-5.1.rst
View file @
91047a9e
...
@@ -199,14 +199,15 @@ vcl_backend_response
...
@@ -199,14 +199,15 @@ vcl_backend_response
to a valid storage will set ``beresp.storage`` as well. If the
to a valid storage will set ``beresp.storage`` as well. If the
storage is invalid, ``beresp.storage`` is left untouched.
storage is invalid, ``beresp.storage`` is left untouched.
When multiple storage backends have been defined with the ``-s``
For the case where multiple storage backends have been defined with
command-line option for varnishd, but none is explicitly set in
the ``-s`` command-line option for varnishd, but none is explicitly
``vcl_backend_response``, storage selection and the use of the nuke
set in ``vcl_backend_response``, storage selection and the use of the
limit has been reworked (see :ref:`ref_param_nuke_limit`). Previously,
nuke limit has been reworked (see
a storage backend was tried first with a nuke limit of 0, and retried
:ref:`ref_param_nuke_limit`). Previously, a storage backend was tried
on failure with the limit configured as the ``-p`` parameter
first with a nuke limit of 0, and retried on failure with the limit
``nuke_limit``. When no storage was specified, Varnish went through
configured as the ``-p`` parameter ``nuke_limit``. When no storage was
every one in round-robin order with a nuke limit of 0 before retrying.
specified, Varnish went through every one in round-robin order with a
nuke limit of 0 before retrying.
Now ``beresp.storage`` is initialized with a storage backend before
Now ``beresp.storage`` is initialized with a storage backend before
``vcl_backend_response`` executes, and the storage set in
``vcl_backend_response`` executes, and the storage set in
...
...
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