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
f56d1bf3
Unverified
Commit
f56d1bf3
authored
Mar 14, 2022
by
Nils Goroll
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Release docs: Mark changes introduced with 7.0.1
parent
8c4b8def
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
6 deletions
+7
-6
changes-trunk.rst
doc/sphinx/whats-new/changes-trunk.rst
+7
-6
No files found.
doc/sphinx/whats-new/changes-trunk.rst
View file @
f56d1bf3
...
...
@@ -97,7 +97,7 @@ Other changes to VCL
Where a regular expression literal is expected, it is now possible to have a
concatenation of constant strings. It can be useful when part of the
expression comes from an environment-specific include, or to break a long
expression into multiple lines.
expression into multiple lines.
(introduced with 7.0.1)
Similarly to ``varnishd`` parameters, it is now possible to have deprecated
aliases of VCL variables. Although there are none so far, aliases will allow
...
...
@@ -153,7 +153,7 @@ environment (service manager, container orchestrator, etc) reacts to a
varnishtest
===========
The ``SO_RCVTIMEO_WORKS`` feature check is gone.
The ``SO_RCVTIMEO_WORKS`` feature check is gone.
(introduced with 7.0.1)
The reporting of ``logexpect`` events was rearranged for readability.
...
...
@@ -165,10 +165,11 @@ on.
Changes for developers and VMOD authors
=======================================
The ``SO_RCVTIMEO`` and ``SO_SNDTIMEO`` socket options are now required at
build time since their absence would otherwise prevent some timeouts to take
effect. We no longer check whether they effectively work, hence the removal of
the ``SO_RCVTIMEO_WORKS`` feature check in ``varnishtest``.
The ``SO_RCVTIMEO`` and ``SO_SNDTIMEO`` socket options are now
required at build time since their absence would otherwise prevent
some timeouts to take effect. We no longer check whether they
effectively work, hence the removal of the ``SO_RCVTIMEO_WORKS``
feature check in ``varnishtest``. (introduced with 7.0.1)
Varnish will use libunwind by default when available at configure time, the
``--without-unwind`` configure flag can prevent this and fall back to
...
...
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