Varnish Cache Plus 6.0.8r3 Release

Published June 15, 2021.

About the release

This is a bugfix release fixing smaller issues, some of which was introduced in the previous feature release.

New features:

  • Increased the MAX_HDR limit in varnishtest from 50 to 256.

Bugs fixed:

  • Fix a vmod_goto bug introduced in 6.0.8r2, where creating two identical dns_director objects would trigger an assert. (VS issue #1176)

  • Fix a NULL pointer dereference in an error handling path in the JWT VMOD.

  • Fix a NULL pointer dereference when setting namespaces in the Accounting VMOD.

  • Fail correctly when the Stat VMOD is attempted called from Client context.

  • Better error handling for workspace errors when allocating fetch and delivery processors. (VS issue #1177)

  • Correct an H/2 buffer handling issue introduced in 6.0.8r2. (VS issue #1182)

See the change log for a full overview of new features and bug fixes in this and previous versions.

Important information when using synthbackend.mirror() in combination with persisted MSE

The synthbackend.mirror() bug could cause corrupted objects before causing Varnish to crash. When using synthbackend.mirror() together with persisted MSE, these corrupted objects could persist after the crash. If you used synthbackend.mirror() together with persisted MSE before 6.0.8r1, then it is recommended to clear the cache on upgrade to this version, unless you have already done so after upgrading to any previous releases after 6.0.8r1.

Important! Third party VMODs need to be recompiled for 6.0.7r1

The ABI for VMODs changed with 6.0.7r1, so every VMOD older than that, needs to be recompiled to work with the new versions. There is no API breakage, so a simple recompile should be sufficient. If you only use VMODs bundled with Varnish Cache Enterprise, you do not have to do anything, as bundled VMODs are always recompiled.