From: William Lallemand <wlallemand@haproxy.org>
Date: Fri, 26 Aug 2022 14:38:43 +0000 (+0200)
Subject: DOC: configuration: do-resolve doesn't work with a port in the string
X-Git-Tag: v2.7-dev5~54
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=1ef2460934bffb86bd32dcdc1d418946cfc809f5;p=thirdparty%2Fhaproxy.git

DOC: configuration: do-resolve doesn't work with a port in the string

Fix the documentation about do-resolve to handle the case where a port
is associated to the hostname in the Host header.

Must be backported as far as 2.0.
---

diff --git a/doc/configuration.txt b/doc/configuration.txt
index fc4f3a4cf2..8f8900b0fb 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -6579,7 +6579,8 @@ http-request do-resolve(<var>,<resolvers>,[ipv4,ipv6]) <expr>
   based on information found in the request (IE a Host header).
   If this action is used to find the server's IP address (using the
   "set-dst" action), then the server IP address in the backend must be set
-  to 0.0.0.0.
+  to 0.0.0.0. The do-resolve action takes an host-only parameter, any port must
+  be removed from the string.
 
   Example:
     resolvers mydns
@@ -6594,7 +6595,7 @@ http-request do-resolve(<var>,<resolvers>,[ipv4,ipv6]) <expr>
 
     frontend fe
       bind 10.42.0.1:80
-      http-request do-resolve(txn.myip,mydns,ipv4) hdr(Host),lower
+      http-request do-resolve(txn.myip,mydns,ipv4) hdr(Host),lower,regsub(:[0-9]*$,)
       http-request capture var(txn.myip) len 40
 
       # return 503 when the variable is not set,