408 Request Timeout
The server did not receive a complete request message within the time that it was prepared to wait.
A server SHOULD send the "close" connection option1 in the response, since 408 implies that the server has decided to close the connection rather than continue waiting. If the client has an outstanding request in transit, the client MAY repeat that request on a new connection.
- 1 Connection RFC7230 Section 6.1
- Source: RFC7231 Section 6.5.7
408 Code References
-
.NET HTTP Status Enum
HttpStatusCode.RequestTimeout -
Rust HTTP Status Constant
http::StatusCode::REQUEST_TIMEOUT -
Rails HTTP Status Symbol
:request_timeout -
Go HTTP Status Constant
http.StatusRequestTimeout -
Symfony HTTP Status Constant
Response::HTTP_REQUEST_TIMEOUT -
Python2 HTTP Status Constant
httplib.REQUEST_TIMEOUT -
Python3+ HTTP Status Constant
http.client.REQUEST_TIMEOUT -
Python3.5+ HTTP Status Constant
http.HTTPStatus.REQUEST_TIMEOUT
