projects / haproxy-3.0.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 286199c) | patch
DOC: config: clarify the fact that SNI should not be used in HTTP scenarios
authorWilly Tarreau <w@1wt.eu>
Fri, 25 Nov 2022 09:12:12 +0000 (10:12 +0100)
committerWilly Tarreau <w@1wt.eu>
Fri, 25 Nov 2022 09:14:12 +0000 (10:14 +0100)
commitd26fb57e817da6cb587c0b61baf60a011e756c49
tree3137fa72e49948fba20f88732d10fc4f155efa6btree | snapshot
parent286199c24ff9fecb1a2c502a490ad9256c621202commit | diff
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.
doc/configuration.txt diff | blob | history
haproxy-3.0 public tree. Stable production code.