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
8c4b8def
Unverified
Commit
8c4b8def
authored
Mar 14, 2022
by
Nils Goroll
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Release docs: polish
parent
7048a238
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
27 additions
and
21 deletions
+27
-21
changes-trunk.rst
doc/sphinx/whats-new/changes-trunk.rst
+9
-6
upgrading-trunk.rst
doc/sphinx/whats-new/upgrading-trunk.rst
+18
-15
No files found.
doc/sphinx/whats-new/changes-trunk.rst
View file @
8c4b8def
...
...
@@ -72,13 +72,14 @@ raised.
Changes to VCL
==============
It is now possible to assign a ``B
ODY`` variable with either a ``STRING`` type
or a ``BLOB``
.
It is now possible to assign a ``B
LOB`` value to a ``BODY`` variable,
in addition to ``STRING`` as before
.
VCL variables
~~~~~~~~~~~~~
New VCL variables to track the beginning of HTTP messages:
New VCL timestamp variables have been added to track the point in time
when HTTP messages were created:
- ``req.time``
- ``req_top.time``
...
...
@@ -87,7 +88,8 @@ New VCL variables to track the beginning of HTTP messages:
- ``beresp.time``
- ``obj.time``
New ``req.transport`` which returns "HTTP/1" or "HTTP/2" as appropriate.
The new ``req.transport`` variable returns "HTTP/1" or "HTTP/2" as
appropriate.
Other changes to VCL
~~~~~~~~~~~~~~~~~~~~
...
...
@@ -193,8 +195,9 @@ When the ``+workspace`` debug flag is raised, workspace logs are no longer
emitted as raw logs disconnected from the task. Having workspace logs grouped
with the rest of the task should help workspace footprint analysis.
It is possible to generate of arbitrary log lines with ``vtc.vsl_replay()``,
which can help testing log processing utilities.
It is now possible to generate arbitrary log lines with ``vtc.vsl()``
and ``vtc.vsl_replay()``, which can help testing log processing
utilities.
It is also possible to tweak the VXID cache chunk size per thread pool with
the ``debug.xid`` command for the Varnish CLI, which can also help testing
...
...
doc/sphinx/whats-new/upgrading-trunk.rst
View file @
8c4b8def
...
...
@@ -53,16 +53,18 @@ a shorthand for ``vsm_space`` is also no longer accepted.
Command line options
~~~~~~~~~~~~~~~~~~~~
A common pattern when a CLI script is used during startup is to combine the
``-I`` option with ``-f ''`` to prevent prevent an automatic startup of the
cache process. In this case a start command is usually present in the CLI
script, most likely as the last command.
This enables loading VCLs and potentially VCL labels which require a specific
order if the active VCL is supposed to switch execution to labels. VCL loaded
through the CLI script is no longer implicitly used if there is no active VCL
yet. If no VCL was loaded through the ``-b`` or ``-f`` options it means that
an explicit ``vcl.use`` command is needed before the ``start`` command.
A common pattern when a CLI script is used during startup is to
combine the ``-I`` and ``-f ''`` options to prevent an automatic
startup of the cache process. In this case a start command is usually
present in the CLI script, most likely as the last command. This
enables loading VCLs and potentially VCL labels which require a
specific order if the active VCL is supposed to switch execution to
labels.
To support this pattern, a VCL loaded through the CLI script is no
longer implicitly used if there is no active VCL yet. If no VCL was
loaded through the ``-b`` or ``-f`` options it means that an explicit
``vcl.use`` command is needed before the ``start`` command.
In the scenario described above, that would already be the case since the
desired active VCL would likely need to be loaded last, not eligible for an
...
...
@@ -118,14 +120,15 @@ of reference counting with ``VRT_StaticDirector()``.
Filters
~~~~~~~
Two new functions ``VRT_AddFilter()`` and ``VRT_RemoveFilter()`` manage
filters as pairs. When used as pairs, the filters must have the same name,
otherwise operating with only one fetch or delivery filter is fine.
Two new functions ``VRT_AddFilter()`` and ``VRT_RemoveFilter()``
manage filters as VDP/VFP pairs. When used as pairs, the filters must
have the same name, otherwise operating with only one fetch or
delivery filter is fine.
Unlike its deprecated predecessors ``VRT_AddVFP()`` and ``VRT_AddVDP()``,
the new ``VRT_AddFilter()`` returns an error string. The ``VRT_RemoveVFP()``
and ``VRT_RemoveVDP()`` functions are also deprecated an
simply thin wrapper
lacking error handling around the new functions
.
and ``VRT_RemoveVDP()`` functions are also deprecated an
d kept for now
as wrappers of ``VRT_RemoveFilter()`` without error handling
.
VMOD deprecated aliases
~~~~~~~~~~~~~~~~~~~~~~~
...
...
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