From: Christopher Faulet Date: Tue, 6 Apr 2021 07:01:09 +0000 (+0200) Subject: DOC: Explicitly state only IPv4 are supported by forwardfor/originalto options X-Git-Tag: v2.3.10~28 X-Git-Url: http://git.haproxy.org/?a=commitdiff_plain;h=eac279f241289b25cc469daf04e4c309e0eb0dcb;p=haproxy-2.3.git DOC: Explicitly state only IPv4 are supported by forwardfor/originalto options IPv6 support was added in the 2.4. However, on previous versions, it is not explicit that only IPv4 addresses are supported. In addition, a workaround solution is proposed to add IPv6 addresses. This patch is related to issue #1145. There is no upstream commit ID. It may be backported to any stable versions. --- diff --git a/doc/configuration.txt b/doc/configuration.txt index c0fed55..97a02eb 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -7837,6 +7837,9 @@ option forwardfor [ except ] [ header ] [ if-none ] environment, as this might cause a security issue if headers reaching haproxy are under the control of the end-user. + Only IPv4 addresses are supported. "http-request add-header" or "http-request + set-header" rules may be used to work around this limitation. + This option may be specified either in the frontend or in the backend. If at least one of them uses it, the header will be added. Note that the backend's setting of the header subargument takes precedence over the frontend's if @@ -8632,6 +8635,9 @@ option originalto [ except ] [ header ] network will not cause an addition of this header. Most common uses are with private networks or 127.0.0.1. + Only IPv4 addresses are supported. "http-request add-header" or "http-request + set-header" rules may be used to work around this limitation. + This option may be specified either in the frontend or in the backend. If at least one of them uses it, the header will be added. Note that the backend's setting of the header subargument takes precedence over the frontend's if