Set a read timeout to determine how long an edge server requesting content from your origin server should wait for a response.
How it works
If the edge server doesn't receive a response from your origin before the timeout expiration, a 504 Gateway Timeout error is returned to the client. You can include this to override the default timeout that a requesting client, such as a browser uses. For example, you could:
- Set a shorter time so an end user isn't waiting too long for your requested content and instead is sent an error so they can retry the request.
- Set a longer time if you don't want a browser to use its default timeout and timeout too early.
Note that this timeout is separate from the Connect Timeout behavior. Connect Timeout covers the time it takes for a connection to be established between the edge server and your origin server, before the edge server even sends the request.
You should contact your Akamai account team for help configuring this behavior.
Features and options
|Field||What it does|
|Timeout||Set the read timeout from 1 through 599 seconds, or from 1 through 9 minutes. This value should never be zero. The default value is 120 seconds.|
Updated about 2 months ago