- Home
- Tools
- Developer Tools
- HTTP Status Codes
- 408 Request Timeout
408 Request Timeout
The server waited for the client to finish sending its request, gave up and is closing the connection.
- Class
- 4xx Client error. The request is the problem: a wrong address, missing credentials, data the server can't accept.
- Defined in
- RFC 9110
What causes it
When the request arrives too slowly or not completely: an upload over a bad connection, a client that opened a connection and then sent nothing. Servers also use it when they close a connection that has been idle for too long.
What to do about it
Try again. The client is allowed to repeat the request on a new connection, and for a one-off 408 that is all there is to it.
If it happens with uploads, the connection is too slow for the time limit of the server. Send smaller pieces, or have the limit raised: in nginx these are client_body_timeout and client_header_timeout, 60 seconds each by default.
The code says nothing about how long the server took to answer. That is a 504.
Not to be confused with
| 504 Gateway Timeout | A gateway waited too long for the server behind it. |
|---|---|
| 499 Client Closed Request | The entry in the nginx log for the reverse: the client gave up waiting. |
All codes are on the list of HTTP status codes, which can be searched by number and by word.
Other 4xx 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