408 Request Timeout
The server gave up waiting for the client to complete its request and closed the connection. The client may retry with a fresh connection.
What it means
408 Request Timeout means the client was too slow sending the request — often an idle keep-alive connection the server reclaimed. A well-behaved server sends Connection: close, and the client may safely retry on a new connection.
Why it matters
- It frees server resources tied up by slow or stalled clients.
- It signals a retriable condition distinct from server errors.
Common mistakes
- Treating 408 as a server fault; it is about the client not completing in time.
- Retrying on the same dead connection instead of opening a new one.
How WebInspect checks this
- WebInspect measures connection and TTFB timings that help diagnose timeout-prone endpoints.