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
8204df12
Commit
8204df12
authored
Sep 13, 2017
by
Dridi Boukelmoune
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Documentation
parent
17b36d51
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
39 additions
and
3 deletions
+39
-3
upgrading-5.2.rst
doc/sphinx/whats-new/upgrading-5.2.rst
+39
-3
No files found.
doc/sphinx/whats-new/upgrading-5.2.rst
View file @
8204df12
...
@@ -40,10 +40,37 @@ XXX: headline changes ...
...
@@ -40,10 +40,37 @@ XXX: headline changes ...
*XXX: the most important changes or additions first*
*XXX: the most important changes or additions first*
Stricter checking of VCL symbol names
Consistent symbol names
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~
VCL symbols originate from various parts of Varnish: there are built-in
variables, subroutines, functions, and the free-form headers. Symbols
may live in a namespace denoted by the ``'.'`` (dot) character as in
``req.http.Cache-Control``. When you create a VCL label, a new symbol
becomes available, named after the label. Storage backends always have
a name, even if you don't specify one, and they can also be accessed in
VCL: for example ``storage.Transient``.
Because headers and VCL names could contain dashes, while subroutines or
VMOD objects couldn't, this created an inconsistency. All symbols follow
the same rules now and must follow the same (case-insensitive) pattern:
``[a-z][a-z0-9_-]*``.
You can now write code like::
sub my-sub {
new my-obj = my_vmod.my_constuctor(storage.my-store);
}
sub vcl_init {
call my-sub;
}
As you may notice in the example above, it is not possible yet to have
dashes in a vmod symbol.
*XXX: TBD by DB*
Long storage backend names used to be truncated due to a limitation in
the VSC subsystem, this is no longer the case.
``req.hash`` and ``bereq.hash``
``req.hash`` and ``bereq.hash``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
...
@@ -127,6 +154,10 @@ Other changes
...
@@ -127,6 +154,10 @@ Other changes
``vcl_path`` parameter if a relative file name is used, see
``vcl_path`` parameter if a relative file name is used, see
:ref:`varnishd(1)` and :ref:`ref_param_vcl_path`.
:ref:`varnishd(1)` and :ref:`ref_param_vcl_path`.
* The ``-a`` option can now take a name, otherwise a default one
is selected to name the listen address. It may become accessible
in VCL in the future.
* ``varnishstat(1)``:
* ``varnishstat(1)``:
* In curses mode, the top two lines showing uptimes for the
* In curses mode, the top two lines showing uptimes for the
...
@@ -160,6 +191,11 @@ Other changes
...
@@ -160,6 +191,11 @@ Other changes
See :ref:`vsl(7)`.
See :ref:`vsl(7)`.
* The ``SessOpen`` log record displays the name of the listen address
instead of the endpoint in its 3rd field.
See :ref:`vsl(7)`.
* ``varnishtest(1)`` and ``vtc(7)``:
* ``varnishtest(1)`` and ``vtc(7)``:
* *XXX: changes in test scripting or test code, for example due to VMOD vtc?*
* *XXX: changes in test scripting or test code, for example due to VMOD vtc?*
...
...
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