From f9515def9288651a6c1817f0f2d042d9078205a0 Mon Sep 17 00:00:00 2001 From: Evilham Date: Sat, 30 Oct 2021 12:49:00 +0200 Subject: [PATCH] [__haproxy_dualstack] Improve manpage --- type/__haproxy_dualstack/man.rst | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/type/__haproxy_dualstack/man.rst b/type/__haproxy_dualstack/man.rst index 901eeda..6c131cb 100644 --- a/type/__haproxy_dualstack/man.rst +++ b/type/__haproxy_dualstack/man.rst @@ -17,7 +17,7 @@ one IPv4 for many such services. By default this type uses the plain TCP proxy mode, which means that there is no need for TLS termination on this host when SNI is supported. -This also means that proxied service will not receive the client's IP address, +This also means that proxied services will not receive the client's IP address, but will see the proxy's IP address instead (that of `$__target_host`). This can be solved by using the PROXY protocol, but do take into account that, @@ -30,7 +30,6 @@ serve HTTP and HTTPS using the PROXY protocol. See the EXAMPLES for more details. - OPTIONAL PARAMETERS ------------------- v4proxy @@ -103,9 +102,9 @@ EXAMPLES SEE ALSO -------- +- https://www.haproxy.com/blog/enhanced-ssl-load-balancing-with-server-name-indication-sni-tls-extension/ - https://www.haproxy.com/blog/haproxy/proxy-protocol/ - https://docs.nginx.com/nginx/admin-guide/load-balancer/using-proxy-protocol/ -- https://www.haproxy.com/blog/enhanced-ssl-load-balancing-with-server-name-indication-sni-tls-extension/ AUTHORS