408 Request Timeout

Estimated reading: 2 minutes 1091 views

This error response indicates that the server is attempting to end an idle connection. This usually occurs when the request takes longer than the time allowed by the server.

Idle connection timeouts can occur when the server is under heavy traffic. This error can also occur if a process takes to long due to a corrupted request.

Since browsers have been using pre-connection methods to speed up the browsing experience for users this error has become more common for end users to see. In some cases the servers may end the connection without sending the error.

If a user encounters this error and it’s likely due to high traffic, then it is recommended to reattempt the request at a later time. If the issue persists or is unexpected then it’s best to contact the server support.

The HyperText Transfer Protocol (HTTP) 408 Request Timeout response status code means that the server would like to shut down this unused connection. It is sent on an idle connection by some servers, even without any previous request by the client.

A server should send the “close” Connection header field in the response, since 408 implies that the server has decided to close the connection rather than continue waiting.

This response is used much more since some browsers, like Chrome, Firefox 27+, and IE9, use HTTP pre-connection mechanisms to speed up surfing.

Note: some servers merely shut down the connection without sending this message.


408 Request Timeout


RFC 7231, section 6.5.7: 408 Request TimeoutHypertext Transfer Protocol (HTTP/1.1): Semantics and Content