SearchThis release contains new features and bug fixes.
In this release, a new version of cluster.vcl is included. We have
designed the new version such that upgrading should not significantly
change existing setups, but bring new features and improvements.
However, we cannot foresee all ways customers have integrated with,
and configured the cluster VCL logic, so it is important that you test
the new version of cluster.vcl before you deploy to production, or
at least review the changes to understand how the new version affects
you.
For MSE4 users, we have a few bug fixes and a significant performance improvement in the ban journaling code.
We also want to remind you that MSE4 is new, and that the binary format for the persisted caches may change. When the binary format changes, you will have to reset your persistent stores, dropping the cache content in the process. (We want to do this as few times as possible, but it is likely that it will happen at least once.)
Important: All users of Varnish Enterprise upgrading from version 6.0.12r9 or lower are encouraged to test their VCL with this release before upgrading. If you encounter VCL compilation failures due to invalid VMOD usage, you will need to update your VCL before upgrading. If this VCL has never caused a problem for you before, it is likely that this VCL code was never reached.
Important: All users of Varnish Enterprise in-process TLS upgrading from version 6.0.13r1 or lower are encouraged to test their HTTPS setup before upgrading. New stricter coherence checks could prevent a restart of the service. If a certificate was loaded with incompatible ciphers, these ciphers could not be presented during a handshake. They must be removed from the configuration from 6.0.13r2 on.
Please see the Changelog for the complete list of changes.