Skip to content

V
varnish-cache
Commit d2014e93 authored by Nils Goroll's avatar Nils Goroll
Browse files
Options

clarify that we will not see piped connections ever again

parent 1b72b668
Show whitespace changes
Inline Side-by-side
Showing with 4 additions and 3 deletions
doc/sphinx/users-guide/vcl-built-in-subs.rst
View file @ d2014e93
...@@ -43,11 +43,12 @@ of the following keywords: ...@@ -43,11 +43,12 @@ of the following keywords:
vcl_pipe vcl_pipe
~~~~~~~~ ~~~~~~~~
Called upon entering pipe mode. In this mode, the request is passed Called upon entering pipe mode. In this mode, the request is passed on
on to the backend, and any further data from either client or backend to the backend, and any further data from both the client and backend
is passed on unaltered until either end closes the is passed on unaltered until either end closes the
connection. Basically, Varnish will degrade into a simple TCP proxy, 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 The `vcl_pipe` subroutine may terminate with calling ``return()`` with one
of the following keywords: of the following keywords:
......
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