[5.2] 6b45072 Editorial: change a section heading in Upgrading to 5.2.
PÃ¥l Hermunn Johansen
hermunn at varnish-software.com
Fri Sep 15 11:17:28 UTC 2017
commit 6b45072885c61c46dc94541294f7d7a41e806864
Author: Geoff Simmons <geoff at uplex.de>
Date: Thu Sep 14 08:45:49 2017 +0200
Editorial: change a section heading in Upgrading to 5.2.
server.identity is not a new VCL variable.
diff --git a/doc/sphinx/whats-new/upgrading-5.2.rst b/doc/sphinx/whats-new/upgrading-5.2.rst
index 8b23e6c..364cc01 100644
--- a/doc/sphinx/whats-new/upgrading-5.2.rst
+++ b/doc/sphinx/whats-new/upgrading-5.2.rst
@@ -72,8 +72,8 @@ dashes in a vmod symbol.
Long storage backend names used to be truncated due to a limitation in
the VSC subsystem, this is no longer the case.
-New VCL variables
-~~~~~~~~~~~~~~~~~
+VCL variables
+~~~~~~~~~~~~~
``req.hash`` and ``bereq.hash``
-------------------------------
@@ -109,11 +109,11 @@ not set). See :ref:`varnishd(1)`.
``bereq.is_bgfetch``
--------------------
-``bereq.is_bgfetch`` is readable in backend contexts, and is true if
-the fetch takes place in the background. That is, it is true if
-Varnish found a response in the cache whose TTL was expired, but was
-still in grace time. Varnish returns the stale cached response to the
-client, and initiates the background fetch to refresh the cache
+Added ``bereq.is_bgfetch``, which is readable in backend contexts, and
+is true if the fetch takes place in the background. That is, it is
+true if Varnish found a response in the cache whose TTL was expired,
+but was still in grace time. Varnish returns the stale cached response
+to the client, and initiates the background fetch to refresh the cache
object.
XXX: vcl_sub_XXX ...
More information about the varnish-commit
mailing list