Skip to the content

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

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

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 TimeoutA gateway waited too long for the server behind it.
499 Client Closed RequestThe 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.

See all 12