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
2e964eb2
Commit
2e964eb2
authored
May 15, 2015
by
Lasse Karstensen
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document new TCP endpoint variables.
parent
2679bb6d
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
13 additions
and
0 deletions
+13
-0
changes.rst
doc/sphinx/whats-new/changes.rst
+13
-0
No files found.
doc/sphinx/whats-new/changes.rst
View file @
2e964eb2
...
...
@@ -78,6 +78,19 @@ The ``-a`` startup argument syntax has been expanded to allow for this::
Both PROXY1 and PROXY2 protocols are supported on the resulting listening
socket.
For connections coming in over a PROXY socket, ``client.ip`` and
``server.ip`` will contain the adresses given to Varnish in the PROXY
header/preamble. (the "real" client IP.)
The new VCL variables ``remote.ip`` and ``local.ip`` contains the local TCP
connection endpoints. On non-PROXY connections these will be identical to
``client.ip`` and ``server.ip``.
An expected pattern following this is `if (std.port(local.ip) == 80) { }` in
``vcl_recv`` to see if traffic came in over the HTTP listening socket. (so a client
redirect to HTTPS can be served.)
VMOD backends
=============
...
...
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