Idle Timeout
Summary
If you are proxying long-lived requests that employ streaming calls such as websockets or gRPC, set Idle Timeout to either a maximum value there may be no data exchange over a connection (recommended), or set it to unlimited (0s).
If idle_timeout is specified, and route timeout is not explicitly set, then the route timeout would be unlimited (0s). You still may specify maximum lifetime of the connection using the route timeout value (i.e. to 1 day).
How to configure
- Core
- Enterprise
- Kubernetes
| YAML/JSON setting | Type | Usage | Default |
|---|---|---|---|
idle_timeout | string (Go Duration formatting) | optional | 5m |
Set Idle Timeout under route Timeouts settings in the Console:
See the Kubernetes Ingress - Pomerium Standard Annotations section for more information.
routes:
- from: https://verify.localhost.pomerium.io
to: http://verify:8000
timeout: 1m
idle_timeout: 5m