aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2025-06-10 01:39:15 +0000
committerLaurent Bercot <ska@appnovation.com>2025-06-10 01:39:15 +0000
commit5db792ba17ce1c372ece1a9d4b152290d4f1b867 (patch)
tree7a2e186b483cc82ca509ff5033d90ce2015352a1 /doc
parent992508c00caddc5576968bad88b6e6f01344e472 (diff)
downloads6-networking-5db792ba17ce1c372ece1a9d4b152290d4f1b867.tar.gz
proxy-server: support in s6-tlsserver
Signed-off-by: Laurent Bercot <ska@appnovation.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/s6-tlsserver.html14
1 files changed, 13 insertions, 1 deletions
diff --git a/doc/s6-tlsserver.html b/doc/s6-tlsserver.html
index 6f199e7..27bcc66 100644
--- a/doc/s6-tlsserver.html
+++ b/doc/s6-tlsserver.html
@@ -139,13 +139,25 @@ variables will not appear in <em>prog</em>'s environment.
<h2> Options </h2>
<p>
- <tt>s6-tlsserver</tt> accepts a myriad of options, all of which are
+ <tt>s6-tlsserver</tt> accepts a myriad of options, most of which are
passed as is to the correct executable. Not giving any options will
generally work, but unless you're running a very public server
(such as a Web server) or base your access control on client
certificates, you probably still want TCP access rules.
</p>
+<h3> Options informing s6-tlsserver behaviour </h3>
+
+<ul>
+ <li> <tt>-L</tt>&nbsp;: if this option is given, s6-tlsserver will
+add an invocation of <a href="proxy-server.html">proxy-server</a> so that
+a PROXY line or binary block is read <em>in cleartext</em> before the
+TLS tunnel is established. If the proxy uses the v2 version of the PROXY
+protocol and transmits SSL information from the client connection, this
+information will be reflected in the SSL environment variables transmitted
+to <em>prog</em>. </li>
+</ul>
+
<h3> Options passed as is to s6-tcpserver </h3>
<ul>