Commit 229aadc6 authored by Nils Goroll's avatar Nils Goroll

doc: vcl_deliver {}

parent f08472bb
...@@ -19,7 +19,7 @@ SYNOPSIS ...@@ -19,7 +19,7 @@ SYNOPSIS
import pesi; import pesi;
# Enable parallel ESI processing in vcl_deliver. # Enable parallel ESI processing in vcl_deliver {}.
VOID pesi.activate() VOID pesi.activate()
# Set a boolean configuration parameter. # Set a boolean configuration parameter.
...@@ -70,7 +70,7 @@ composition in a standard Varnish deployment does not depend on the ...@@ -70,7 +70,7 @@ composition in a standard Varnish deployment does not depend on the
serial order, then it will work the same way with VDP pesi. serial order, then it will work the same way with VDP pesi.
Parallel ESI processing is enabled by invoking ``pesi.activate()`` in Parallel ESI processing is enabled by invoking ``pesi.activate()`` in
``vcl_deliver``:: ``vcl_deliver {}``::
import pesi; import pesi;
...@@ -111,9 +111,9 @@ $Function VOID activate() ...@@ -111,9 +111,9 @@ $Function VOID activate()
Enable parallel ESI processing for the client response. Enable parallel ESI processing for the client response.
``activate()`` MUST be called in ``vcl_deliver`` only. If it is called ``activate()`` MUST be called in ``vcl_deliver {}`` only. If it is
in any other VCL subroutine, VCL failure is invoked (see `ERRORS`_ called in any other VCL subroutine, VCL failure is invoked (see
below for details). `ERRORS`_ below for details).
If ``activate()`` is called on *any* ESI level (any depth of include If ``activate()`` is called on *any* ESI level (any depth of include
nesting), then it MUST be called on *all* levels of the response. If nesting), then it MUST be called on *all* levels of the response. If
...@@ -131,8 +131,8 @@ URLs are different at different ESI levels). ...@@ -131,8 +131,8 @@ URLs are different at different ESI levels).
See the documentation of ``set()`` below for a way to choose serial See the documentation of ``set()`` below for a way to choose serial
ESI processing for all of the includes in the response at the current ESI processing for all of the includes in the response at the current
ESI level. Even then, ``activate()`` must be called in ``vcl_deliver`` ESI level. Even then, ``activate()`` must be called in ``vcl_deliver
in addition to ``set()``. {}`` in addition to ``set()``.
As with standard Varnish, ESI processing can be selectively disabled As with standard Varnish, ESI processing can be selectively disabled
for a client response, by setting ``resp.do_esi`` to ``false`` in VCL for a client response, by setting ``resp.do_esi`` to ``false`` in VCL
...@@ -197,7 +197,7 @@ identified by the ENUM ``parameter``. Currently the parameters can ...@@ -197,7 +197,7 @@ identified by the ENUM ``parameter``. Currently the parameters can
only be set with a boolean value in ``bool`` (but future versions of only be set with a boolean value in ``bool`` (but future versions of
this function may allow for setting other data types). this function may allow for setting other data types).
``set()`` MUST be called in ``vcl_deliver`` only; otherwise VCL ``set()`` MUST be called in ``vcl_deliver {}`` only; otherwise VCL
failure is invoked (see `ERRORS`_). failure is invoked (see `ERRORS`_).
The parameters that can be set are currently ``serial`` and ``thread``: The parameters that can be set are currently ``serial`` and ``thread``:
......
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