408 Request Timeout
The server timed out waiting for the request to be sent in full.
| Class | Client error (4xx) |
|---|---|
| Defined in | RFC9110, Section 15.5.9 |
| Cacheable by default | No, unless explicit freshness headers allow it |
Common causes
- The client was too slow to send the full request.
- An unstable connection, or an idle connection closed by the server.
What to do
Retry the request. If it happens often, check network quality and server timeout settings.
Related codes
- 504 Gateway Timeout: A gateway or proxy did not get a response from the upstream server in time.
- 400 Bad Request: The server cannot process the request because it looks malformed.
- 429 Too Many Requests: The client has sent too many requests in a given amount of time (rate limiting).