document the controller tcp listener and its two leaves
This commit is contained in:
parent
187ed82de0
commit
cd786ef401
1 changed files with 83 additions and 1 deletions
|
|
@ -472,6 +472,13 @@ the opposite arm run as a control:
|
|||
that's every service on the hive.
|
||||
- `server_name on` — sends SNI, or the far end can't pick a cert.
|
||||
|
||||
`verifiedProxyToWithClientCert name { certificate, key }` is the same block plus
|
||||
`proxy_ssl_certificate` and `proxy_ssl_certificate_key`, for an upstream that demands a client
|
||||
certificate. The swarm UI's `/api/` and `/webhook/forge/` locations use it when the swarm
|
||||
controller's TCP listener is on (`swarm.controller.tcp.enable`); `certificate` and `key` are host
|
||||
paths nginx can read. `verifiedProxyTo` itself presents no client certificate, and every other
|
||||
caller keeps rendering exactly what it did.
|
||||
|
||||
**⚠️ Session-cache footgun**: the module leaves `proxy_ssl_session_reuse` at its
|
||||
default (on), deliberately — nginx uses this on per-request auth
|
||||
subrequests, so every request pays the handshake it avoids. Worth
|
||||
|
|
|
|||
Loading…
Reference in a new issue