tree 1c0757943019e6974013cb534031087d30ba4d63
parent ee9afa2be608df86ebcb2b20b1a63bcbe398eaee
author Willy Tarreau <w@1wt.eu> 1669367532 +0100
committer Christopher Faulet <cfaulet@haproxy.com> 1670489828 +0100

DOC: config: clarify the fact that SNI should not be used in HTTP scenarios

As reported by Tim in issue #1373 some warnings are deserved to explain
why using the frontend SNI for routing or connecting to a server is
usually not correct, especially since it can be tempting and used to
make sense in pure TCP scenarios.

(cherry picked from commit d26fb57e817da6cb587c0b61baf60a011e756c49)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit 0b41d6be9bf7d8a091ddcb8a6630ff747f63ee87)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit 2dc31601680f934f18dd6b3575ae33612299f39a)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>