Commit 9d58364e authored by Geoff Simmons's avatar Geoff Simmons

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

parent c138645f
...@@ -184,6 +184,24 @@ same XID shown in the log for session transactions (with ...@@ -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 ``-g session`` grouping). ``sess.xid`` is read-only and is available
as of VCL 4.1. 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 Unix domain sockets and VCL
~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment