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
b486bf47
Commit
b486bf47
authored
Nov 24, 2021
by
Martin Blix Grydeland
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
More changelog entries
parent
be077d4a
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
0 deletions
+12
-0
changes.rst
doc/changes.rst
+12
-0
No files found.
doc/changes.rst
View file @
b486bf47
...
...
@@ -49,11 +49,23 @@ Varnish Cache 6.0.9 (unreleased)
* Add an option to `configure` to use `libunwind` for the stack backtrace
in the panic output. (3717_)
* A bug in ``vmod_blob`` for base64 decoding with a ``length`` argument
and non-padding decoding has been fixed (3378_)
* The socket option inheritance checks now correctly identifies situations
where UDS and TCP listening sockets behave differently, and are no
longer subject to the order the inheritance checks happens to be
executed (3732_).
* IPv6 listen endpoint address strings are now printed using brackets.
.. _3617: https://github.com/varnishcache/varnish-cache/pull/3617
.. _3437: https://github.com/varnishcache/varnish-cache/issues/3437'
.. _3564: https://github.com/varnishcache/varnish-cache/issues/3564'
.. _3716: https://github.com/varnishcache/varnish-cache/pull/3716'
.. _3717: https://github.com/varnishcache/varnish-cache/pull/3717'
.. _3378: https://github.com/varnishcache/varnish-cache/issues/3378'
.. _3732: https://github.com/varnishcache/varnish-cache/pull/3732
================================
Varnish Cache 6.0.8 (2021-07-13)
...
...
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