[master] 9d58364 Document 4.0->4.1 VCL variable changes in "Upgrading to 6.0".

Geoff Simmons geoff at uplex.de
Tue Mar 13 19:27:10 UTC 2018

commit 9d58364eedbff7c03abb0ff25e3391539e276d94
Author: Geoff Simmons <geoff at uplex.de>
Date:   Tue Mar 13 20:25:06 2018 +0100

    Document 4.0->4.1 VCL variable changes in "Upgrading to 6.0".

diff --git a/doc/sphinx/whats-new/upgrading-6.0.rst b/doc/sphinx/whats-new/upgrading-6.0.rst
index 8a5e84a..23e05e7 100644
--- a/doc/sphinx/whats-new/upgrading-6.0.rst
+++ b/doc/sphinx/whats-new/upgrading-6.0.rst
@@ -184,6 +184,24 @@ same XID shown in the log for session transactions (with
 ``-g session`` grouping). ``sess.xid`` is read-only and is available
 as of VCL 4.1.
+Variable changes in VCL 4.0 and 4.1
+The ``*.proto`` variables (``req.proto``, ``resp.proto``,
+``bereq.proto`` and ``beresp.proto``) are read-only as of VCL 4.1, but
+are still writable in VCL 4.0.
+``req.esi`` is available in VCL 4.0, but no longer in 4.1. In its
+place, ``resp.do_esi`` has been introduced in VCL 4.1. Set
+``resp.do_esi`` to false in ``vcl_deliver`` if you want to selectively
+disable ESI processing for a client response (even though
+``beresp.do_esi`` was true during fetch).
+``beresp.backend.ip`` and ``beresp.storage_hint`` are discontinued as
+of VCL 4.1, but are still available in 4.0. Note that
+``beresp.storage_hint`` has been deprecated since Varnish 5.1; you
+should use ``beresp.storage`` instead.
 Unix domain sockets and VCL

More information about the varnish-commit mailing list