You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update the Read Timeout and Write Timeout descriptions. Call out the
special behavior of the 0 value for all three. Add a sentence to
discourage turning off the Read Timeout.
Copy file name to clipboardexpand all lines: content/docs/reference/global-timeouts.mdx
+17-9
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,9 @@ You can set also set [route-level timeouts](/docs/reference/routes/timeouts).
25
25
26
26
## Read Timeout
27
27
28
-
**Read Timeout** sets the maximum amount of time for the client to receive an entire HTTP request stream.
28
+
**Read Timeout** sets the maximum amount of time for a downstream client to complete a single HTTP request. The time starts when a request is begun and ends either when Pomerium has proxied the entire request body to the upstream service, or when Pomerium has begun sending a response back to the client.
29
+
30
+
This timeout is disabled if set to `0`. (This is not recommended, as a malicious client could consume significant resources by beginning many incomplete requests.)
29
31
30
32
### How to configure
31
33
@@ -34,7 +36,7 @@ You can set also set [route-level timeouts](/docs/reference/routes/timeouts).
**Write Timeout** sets the maximum time that a stream’s lifetime will span. An HTTP request/response exchange fully consumes a single stream. So, the `write_timeout` value must be greater than `read_timeout`, as it covers both the HTTP request and response time.
75
+
**Write Timeout** sets the maximum time for a single HTTP request/response pair to fully complete. This should be greater than the [**Read Timeout**](#read-timeout) setting as this includes both the request and response time.
0 commit comments