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
1aa3c8cc
Unverified
Commit
1aa3c8cc
authored
Mar 14, 2021
by
Nils Goroll
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
whats-new: upgrading
parent
00da7068
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
55 additions
and
23 deletions
+55
-23
changes-trunk.rst
doc/sphinx/whats-new/changes-trunk.rst
+3
-4
upgrading-trunk.rst
doc/sphinx/whats-new/upgrading-trunk.rst
+52
-19
No files found.
doc/sphinx/whats-new/changes-trunk.rst
View file @
1aa3c8cc
...
@@ -3,10 +3,6 @@
...
@@ -3,10 +3,6 @@
SPDX-License-Identifier: BSD-2-Clause
SPDX-License-Identifier: BSD-2-Clause
See LICENSE file for full text of license
See LICENSE file for full text of license
**Note: This is a working document for a future release, with running
updates for changes in the development branch. For changes in the
released versions of Varnish, see:** :ref:`whats-new-index`
.. _whatsnew_changes_CURRENT:
.. _whatsnew_changes_CURRENT:
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
...
@@ -195,6 +191,8 @@ usage pattern with the new interface is::
...
@@ -195,6 +191,8 @@ usage pattern with the new interface is::
return(synth(400, std.ban_error()));
return(synth(400, std.ban_error()));
}
}
.. _whatsnew_changes_CURRENT_cookie:
``cookie`` functions
``cookie`` functions
~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~
...
@@ -344,6 +342,7 @@ All varnish tools using the VUT library utilities for argument
...
@@ -344,6 +342,7 @@ All varnish tools using the VUT library utilities for argument
processing now support the ``--optstring`` argument to return a string
processing now support the ``--optstring`` argument to return a string
suitable for use with ``getopts`` from shell scripts.
suitable for use with ``getopts`` from shell scripts.
.. _whatsnew_changes_CURRENT_vmod:
Developer: Changes for VMOD authors
Developer: Changes for VMOD authors
===================================
===================================
...
...
doc/sphinx/whats-new/upgrading-trunk.rst
View file @
1aa3c8cc
...
@@ -3,36 +3,69 @@
...
@@ -3,36 +3,69 @@
SPDX-License-Identifier: BSD-2-Clause
SPDX-License-Identifier: BSD-2-Clause
See LICENSE file for full text of license
See LICENSE file for full text of license
**Note: This is a working document for a future release, with running
updates for changes in the development branch. For changes in the
released versions of Varnish, see:** :ref:`whats-new-index`
.. _whatsnew_upgrading_CURRENT:
.. _whatsnew_upgrading_CURRENT:
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Upgrading to Varnish **$NEXT_RELEASE**
Upgrading to Varnish **$NEXT_RELEASE**
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
**XXX: how to upgrade from previous deployments to this
In general, this release should not come with relevant incompatibilies
version. Limited to work that has to be done for an upgrade, new
to the previous release 6.5.
features are listed in "Changes". Explicitly mention what does *not*
have to be changed, especially in VCL. May include, but is not limited
VCL should continue to work as before except when rather exotic,
to:**
partly unintended and/or undocumented features are used.
Header Validation
=================
Varnish now validates any headers set from VCL to contain only
characters allowed by RFC7230. A (runtime) VCL failure is triggered if
not. Such VCL failures, which result in ``503`` responses, should be
investigated. As a last resort, the ``validate_headers`` parameter can
be set to ``false`` to avoid these VCL failures.
BAN changes
===========
* The ``ban_cutoff`` parameter now refers to the overall length of the
ban list, including completed bans, where before only non-completed
("active") bans were counted towards ``ban_cutoff``.
* The ``ban()`` VCL builtin is now deprecated and should be replaced
with :ref:`whatsnew_changes_CURRENT_ban`
Accounting Changes
==================
Accounting statistics and Log records have changed. See
:ref:`whatsnew_changes_CURRENT_accounting` for details.
VMOD ``cookie`` functions
=========================
The regular expression arguments taken by various functions from the
``cookie`` VMOD now need to be literal. See
:ref:`whatsnew_changes_CURRENT_cookie` for details.
Other VCL Changes
=================
*
Elements of VCL that have been removed or are deprecated, or whose
*
The ``resp.proto`` variable is now read-only as it should have been
semantics have changed
.
for long
.
* -p parameters that have been removed or are deprecated, or whose
Changing the protocol is an error and should not be required.
semantics have changed.
* Changes in the CLI.
* Trying to use ``std.rollback()`` from ``vcl_pipe`` now results in
VCL failure.
*
Changes in the output or interpretation of stats or the log, including
*
``return(retry)`` from ``vcl_backend_error {}`` now correctly resets
changes affecting varnishncsa/-hist/-top
.
``beresp.status`` and ``beresp.reason``
.
* Changes that may be necessary in VTCs or in the use of varnishtest.
Changes to VMODs
================
* Changes in public APIs that may require changes in VMODs or VAPI/VUT
Many VMODs will need minor adjustments to work with this release. See
client
s.
:ref:`whatsnew_changes_CURRENT_vmod` for detail
s.
*eof*
*eof*
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