[master] bf77721 Document the impact of UDS on varnishncsa in "Upgrading to 6.0".

Geoff Simmons geoff at uplex.de
Mon Mar 12 17:50:10 UTC 2018

commit bf77721c5fcc3daf77a5a79d64120b822b9fa392
Author: Geoff Simmons <geoff at uplex.de>
Date:   Mon Mar 12 18:49:23 2018 +0100

    Document the impact of UDS on varnishncsa in "Upgrading to 6.0".

diff --git a/doc/sphinx/whats-new/upgrading-6.0.rst b/doc/sphinx/whats-new/upgrading-6.0.rst
index f93b8d2..cffab95 100644
--- a/doc/sphinx/whats-new/upgrading-6.0.rst
+++ b/doc/sphinx/whats-new/upgrading-6.0.rst
@@ -429,6 +429,32 @@ Other changes
     with the backend name field -- the second field in
+* ``varnishncsa(1)``
+  * The ``%h`` formatter (remote host) gets its value from
+    ``ReqStart`` for client requests and ``BackendStart`` for backend
+    requests.  The value will be ```` for client requests when
+    the listener is UDS, and for backend requests when the backend is
+    UDS.
+  * The ``%r`` formatter (first line of the request) is reconstructed
+    in part from the Host request header. For UDS backends, Host may
+    be ```` for the reasons explained above (no client Host
+    header and no ``.host_header`` setting for the backend), so that
+    may appear in the output for ``%r``. You can avoid that with the
+    measures discussed above.
+  * If you have more than one UDS listener and/or more than one UDS
+    backend, and you want to tell them apart in the ``varnishncsa``
+    output (rather than just see ````), use the ``%{VSL}x``
+    formatter to capture the listener name and the backend name.
+    For the listener name, use ``%{VSL:ReqStart[3]}x`` for client logs
+    (the third field of ``ReqStart`` logs).
+    For the backend name, use ``%{VSL:BackendOpen[2]}x`` for backend
+    logs.
 * ``varnishtest(1)`` and ``vtc(7)``:
   * The ``client -connect`` and ``server -listen`` commands in vtc

More information about the varnish-commit mailing list