| Previous | Next |
| HTTP_STATUS_PROXY_AUTH_REQ | HTTP_STATUS_CONFLICT |
HTTP_STATUS_REQUEST_TIMEOUT
The timeout is about the inbound request, not the time spent executing application code. A server can close the connection after 408 because it no longer expects the remaining request bytes.
Check slow clients, idle keep-alive connections, upload rate, reverse-proxy read timeouts, and network interruptions. Retrying is appropriate only after confirming that the request was not processed.
A server can close an idle or incomplete request with 408 when the client does not deliver the full message within its timeout. Distinguish this from a 504, where a gateway timed out waiting for an upstream. Check client upload progress, slow links, request framing, and any proxy timeout that acts before the origin.
Looking for a different code? Search another status or error code.