Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
libvdp-pesi
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Jobs
Commits
Open sidebar
uplex-varnish
libvdp-pesi
Commits
229aadc6
Commit
229aadc6
authored
Aug 28, 2019
by
Nils Goroll
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: vcl_deliver {}
parent
f08472bb
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
8 deletions
+8
-8
vdp_pesi.vcc
src/vdp_pesi.vcc
+8
-8
No files found.
src/vdp_pesi.vcc
View file @
229aadc6
...
...
@@ -19,7 +19,7 @@ SYNOPSIS
import pesi;
# Enable parallel ESI processing in vcl_deliver.
# Enable parallel ESI processing in vcl_deliver
{}
.
VOID pesi.activate()
# Set a boolean configuration parameter.
...
...
@@ -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.
Parallel ESI processing is enabled by invoking ``pesi.activate()`` in
``vcl_deliver``::
``vcl_deliver
{}
``::
import pesi;
...
...
@@ -111,9 +111,9 @@ $Function VOID activate()
Enable parallel ESI processing for the client response.
``activate()`` MUST be called in ``vcl_deliver
`` only. If it is called
in any other VCL subroutine, VCL failure is invoked (see `ERRORS`_
below for details).
``activate()`` MUST be called in ``vcl_deliver
{}`` only. If it is
called in any other VCL subroutine, VCL failure is invoked (see
`ERRORS`_
below for details).
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
...
...
@@ -131,8 +131,8 @@ URLs are different at different ESI levels).
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 level. Even then, ``activate()`` must be called in ``vcl_deliver
``
in addition to ``set()``.
ESI level. Even then, ``activate()`` must be called in ``vcl_deliver
{}``
in addition to ``set()``.
As with standard Varnish, ESI processing can be selectively disabled
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
only be set with a boolean value in ``bool`` (but future versions of
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`_).
The parameters that can be set are currently ``serial`` and ``thread``:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment