Specify passthrough for TCP/TLS in its own section
This commit is contained in:
parent
df351511de
commit
4408c634b0
1 changed files with 10 additions and 4 deletions
|
@ -795,11 +795,10 @@ Services are the target for the router.
|
|||
|
||||
When a TLS section is specified,
|
||||
it instructs Traefik that the current router is dedicated to TLS requests only (and that the router should ignore non-TLS requests).
|
||||
|
||||
By default, Traefik will terminate the SSL connections (meaning that it will send decrypted data to the services),
|
||||
but Traefik can be configured in order to let the requests pass through (keeping the data encrypted), and be forwarded to the service "as is".
|
||||
|
||||
??? example "Configuring TLS Termination"
|
||||
By default, a router with a TLS section will terminate the TLS connections, meaning that it will send decrypted data to the services.
|
||||
|
||||
??? example "Router for TLS requests"
|
||||
|
||||
```toml tab="File (TOML)"
|
||||
## Dynamic configuration
|
||||
|
@ -822,6 +821,13 @@ but Traefik can be configured in order to let the requests pass through (keeping
|
|||
tls: {}
|
||||
```
|
||||
|
||||
#### `passthrough`
|
||||
|
||||
As seen above, a TLS router will terminate the TLS connection by default.
|
||||
However, the `passthrough` option can be specified to set whether the requests should be forwarded "as is", keeping all data encrypted.
|
||||
|
||||
It defaults to `false`.
|
||||
|
||||
??? example "Configuring passthrough"
|
||||
|
||||
```toml tab="File (TOML)"
|
||||
|
|
Loading…
Reference in a new issue