4xx Client Error
Safe to retry
408 Request Timeout
The client took too long to send the complete request, so the server gave up.
What causes it
- A slow upload on a poor connection.
- An idle keep-alive connection being closed — browsers often show this after the fact.
- A client that opened a connection and sent nothing.
How to fix it
- Raise the server read timeout for endpoints that accept large uploads.
- Retry is safe for idempotent requests.
At a glance
- Class
- 4xx Client Error
- Reference
- RFC 9110 §15.5.9
- Standardised
- Yes
- Retry the request?
- Yes, with backoff
Other 4xx client error codes
- 400 Bad Request
- 401 Unauthorized
- 402 Payment Required
- 403 Forbidden
- 404 Not Found
- 405 Method Not Allowed
- 406 Not Acceptable
- 407 Proxy Authentication Required
- 409 Conflict
- 410 Gone
- 411 Length Required
- 412 Precondition Failed
- 413 Content Too Large
- 414 URI Too Long
- 415 Unsupported Media Type
- 416 Range Not Satisfiable
- 417 Expectation Failed
- 418 I'm a teapot
- 421 Misdirected Request
- 422 Unprocessable Content
- 423 Locked
- 424 Failed Dependency
- 425 Too Early
- 426 Upgrade Required
- 428 Precondition Required
- 429 Too Many Requests
- 431 Request Header Fields Too Large
- 451 Unavailable For Legal Reasons
- 499 Client Closed Request