bisco/loadbalancer
1
0
Fork 0
generated from bisco/codex-bootstrap
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: configure sni tcp routes

Browse Source
This commit is contained in:
Alfredo Di Stasio
2026-06-30 10:00:45 +02:00
parent 7dfc23d69e
commit b5beb27623
5 changed files with 52 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/operations.md
+1 -1
View File
@@ -54,4 +54,4 @@ For backends running on the Docker host, use `host.docker.internal:PORT` rather
- TLS passthrough prevents Traefik from inspecting HTTP paths, headers, or certificate contents.
- Backend certificates and renewal jobs must be monitored on each backend.
- The default configuration routes all SNI names to the same backend pool. Use more specific `HostSNI(...)` rules if different names need different pools.
- SNI routing depends on clients sending the expected hostname during the TLS handshake. Clients that connect by IP address or omit SNI will not match hostname-specific routers.