Request Timeout — the server did not receive a complete request in time
What 408 Means
The 408 error on the HTTP Status-Codes indicates request timeout — the server did not receive a complete request in time. This typically occurs due to client connection stalls during an upload.
A 408 Request Timeout indicates that the server waited for the client to finish sending the request but stopped waiting before the request was complete. The server is reachable and responsive, but the request never fully arrived within the allowed time window. This status usually reflects slow networks, interrupted uploads, or idle persistent connections that remained open without enough incoming data.
Technical Background
A 408 is centered on the incoming request stream, not on the application's attempt to produce a response. The server times out while waiting for headers or body bytes from the client side of the connection.
That separates 408 from 504. A 504 happens after a gateway forwards a request upstream and waits too long for a response. A 408 happens earlier, before the server has even received the full request it needs in order to process it.
Common Causes
- Client connection stalls during an upload
- Slow network interrupts request body transfer
- Keep-alive connection stays idle too long
- Proxy closes a slow client connection before completion
Typical Scenarios
- A large upload is interrupted before the request body finishes sending
- A mobile network drops packets while the client is still transmitting data
- A keep-alive connection sits open long enough for the server timeout to expire
What to Know
A 408 is often transient and closely tied to network conditions, connection reuse, or large request bodies. If it appears broadly across many uploads or forms, the pattern usually points to client connectivity, proxy timeout settings, or request size pressure rather than to a broken application route.
Frequently Asked Questions
Common questions about HTTP 408 error
No. A 408 means the server did not receive the full client request in time. A 504 means a gateway did not receive an upstream server response in time.
Yes. Long or interrupted uploads are a common reason for 408 responses because the server eventually stops waiting for the request body to finish arriving.
Usually not. A 408 is often specific to certain requests, client connections, or upload paths rather than a complete application outage.