[master] 5778fc7e5 Move an item about the 2018-08 release from 'Changes' to 'Upgrading'.
Geoff Simmons
geoff at uplex.de
Mon Sep 10 07:17:08 UTC 2018
commit 5778fc7e5f89e0da05c57e0d5ebd87e53caacaf8
Author: Geoff Simmons <geoff at uplex.de>
Date: Mon Sep 10 09:13:38 2018 +0200
Move an item about the 2018-08 release from 'Changes' to 'Upgrading'.
We have settled on using 'Upgrading' to list changes like this, while
'Changes' is a free-form prose overview ("about this release").
diff --git a/doc/sphinx/whats-new/changes-6.1.rst b/doc/sphinx/whats-new/changes-6.1.rst
index 91d4b8491..ee3644694 100644
--- a/doc/sphinx/whats-new/changes-6.1.rst
+++ b/doc/sphinx/whats-new/changes-6.1.rst
@@ -10,8 +10,4 @@ Changes in Varnish 6.1
**XXX**
-Varnish now won't rewrite the content-length header when responding to any HEAD
-request, making it possible to cache HEAD requests independently from the GET
-ones (peviously a HEAD request had to be a pass to avoid this rewriting).
-
*eof*
diff --git a/doc/sphinx/whats-new/upgrading-6.1.rst b/doc/sphinx/whats-new/upgrading-6.1.rst
index af02d291e..bbf1420a1 100644
--- a/doc/sphinx/whats-new/upgrading-6.1.rst
+++ b/doc/sphinx/whats-new/upgrading-6.1.rst
@@ -117,6 +117,11 @@ The ``Host`` header is mandatory for HTTP/1.1, as proscribed by the
HTTP standard. If it is missing, then ``builtin.vcl`` causes a
synthetic 400 "Bad request" response to be returned.
+Varnish now won't rewrite the content-length header when responding to
+any HEAD request, making it possible to cache responses to HEAD
+requests independently from the GET responses (previously a HEAD
+request had to be a pass to avoid this rewriting).
+
You can now provide a string argument to ``return(fail("Foo!"))``,
which can be used in ``vcl_init`` to emit an error message if the VCL
load fails due to the return.
More information about the varnish-commit
mailing list