read_timeout
Version: v2025-01-13 | Includes use: Yes |
---|
Behavior name: Read Timeout
This behavior specifies how long the edge server should wait for a response from the requesting forward server after a connection has already been established.
Default behavior
These samples reflect the behavior's default settings. You can use these as is in your configurations or make adjustments based on the behavior's available options.
data "akamai_property_rules_builder" "read_timeout" {
rules_v2025_02_18 {
name = "Read Timeout"
comments = "Specifies how long the edge server should wait for a response from the requesting forward server after a connection has already been established."
behavior {
read_timeout {
value = "5s"
first_by_timeout = "20s"
}
}
}
}
"behaviors": [
{
"name": "readTimeout",
"options": {
"value": "5s",
"firstByteTimeout": "20s"
}
}
]
Options
Option | Description |
---|---|
value |
The amount of time an edge server should wait for each read statement to return a response from the forward server after a connection has already been established. Larger objects may need many reads, and this timeout applies to each read separately. Any failure to complete a read within this time limit aborts the request and sends a
504 Gateway Timeout error to the client.
|
first_byte_timeout |
The amount of time an edge server should wait for the first byte of the response to be returned from the forward server after a connection has already been established. Instead of continually waiting for the content, edge servers send a
504 Gateway Timeout error to the client. If your origin server is handling high loads and might respond slowly, specify a short timeout. Defaults to 20 seconds. Value range is 1s -599s .
|
Updated 22 minutes ago