| commit | d26fb57e817da6cb587c0b61baf60a011e756c49 | [log] [tgz] |
|---|---|---|
| author | Willy Tarreau <w@1wt.eu> | Fri Nov 25 10:12:12 2022 +0100 |
| committer | Willy Tarreau <w@1wt.eu> | Fri Nov 25 10:14:12 2022 +0100 |
| tree | 3137fa72e49948fba20f88732d10fc4f155efa6b | |
| parent | 286199c24ff9fecb1a2c502a490ad9256c621202 [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.