Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
1a59d8e7
Commit
1a59d8e7
authored
Sep 14, 2014
by
Nils Goroll
Committed by
Lasse Karstensen
Sep 22, 2014
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
clarify that we will not see piped connections ever again
parent
c4d966db
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
3 deletions
+4
-3
vcl-built-in-subs.rst
doc/sphinx/users-guide/vcl-built-in-subs.rst
+4
-3
No files found.
doc/sphinx/users-guide/vcl-built-in-subs.rst
View file @
1a59d8e7
...
...
@@ -43,11 +43,12 @@ of the following keywords:
vcl_pipe
~~~~~~~~
Called upon entering pipe mode. In this mode, the request is passed
on to the backend, and any further data from either client or
backend
Called upon entering pipe mode. In this mode, the request is passed
on
to the backend, and any further data from both the client and
backend
is passed on unaltered until either end closes the
connection. Basically, Varnish will degrade into a simple TCP proxy,
shuffling bytes back and forth.
shuffling bytes back and forth. For a connection in pipe mode, no
other VCL subroutine will ever get called after `vcl_pipe`.
The `vcl_pipe` subroutine may terminate with calling ``return()`` with one
of the following keywords:
...
...
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