HTTP 408 Request Timeout
What a 408 Request Timeout response means, why it happens, and the fastest ways to fix it.
The server gave up waiting for the client to finish sending its request. The connection was idle too long.
- Slow/unstable client connections during uploads.
- Clients that open connections but send slowly (or not at all).
- Retry the request — most clients do automatically.
- For large uploads, use chunking/resumable uploads.
- Server-side, tune client body/header timeout settings.
Notes
HTTP status codes are defined in RFC 9110 (which replaced RFC 7231). The first digit is the class: 1xx informational, 2xx success, 3xx redirection, 4xx client error, 5xx server error.
Same class: 400 · 401 · 403 · 404 · 405 · 409 · 410 · 412 · 413 · 415 · 418 · 422 · 425 · 429 · 431 · 451
All codes: HTTP status code reference
Frequently asked questions
What does HTTP 408 mean?
HTTP 408 Request Timeout: The server gave up waiting for the client to finish sending its request. The connection was idle too long.
How do I fix a 408 error?
Retry the request — most clients do automatically. For large uploads, use chunking/resumable uploads. Server-side, tune client body/header timeout settings.
Is a 408 my fault or the server's?
408 is a client error — the request itself needs to change, though server misconfiguration can also trigger it.