Global Timeouts
Summary
Global Timeouts set the global server timeouts. Timeouts can also be set for individual routes.
How to configure
- Core
- Enterprise
- Kubernetes
| Config file keys | Environment variables | Type | Defaults | Definition |
|---|---|---|---|---|
timeout_read | TIMEOUT_READ | string (Go Duration formatting) | 30s | The amount of time for the entire request stream to be received from the client. |
timeout_write | TIMEOUT_WRITE | string (Go Duration formatting) | 0 | The max stream duration is the maximum time that a stream’s lifetime will span. An HTTP request/response exchange fully consumes a single stream. Therefore, this value must be greater than read_timeout as it covers both request and response time. |
timeout_idle | TIMEOUT_IDLE | string (Go Duration formatting) | 5m | The idle timeout is the time at which a downstream or upstream connection will be terminated if there are no active streams. |
Examples
timeout_read: 30s
TIMEOUT_WRITE=0
Set Global Timeouts in the Console: 
| Parameter name | Type | Defaults | Definition |
|---|---|---|---|
timeouts.read | string (Go Duration formatting) | 30s | The amount of time for the entire request stream to be received from the client. |
timeouts.write | string (Go Duration formatting) | 0 | The max stream duration is the maximum time that a stream’s lifetime will span. An HTTP request/response exchange fully consumes a single stream. Therefore, this value must be greater than read_timeout as it covers both request and response time. |
timeouts.idle | string (Go Duration formatting) | 5m | The idle timeout is the time at which a downstream or upstream connection will be terminated if there are no active streams. |
Examples
timeouts:
read: 30s
timeouts:
write: 0
timeouts:
idle: 5m