408
Request Timeout
The server timed out waiting for the client to finish sending the request. The client opened a connection but did not complete the request within the server's timeout window.
What does HTTP 408 mean?
The server timed out waiting for the client to finish sending the request. The client opened a connection but did not complete the request within the server's timeout window.
Common causes
- 1
The client's network connection is slow or unstable, causing the request to take too long to transmit.
- 2
A large file upload exceeds the server's timeout for receiving the request body.
- 3
The client opened a keep-alive connection but did not send a follow-up request within the idle timeout period.
How to fix it
- 1
Check your network connection. Retry the request on a stable connection. If uploading large files, consider chunked uploads.
- 2
Increase the server's client_body_timeout (nginx) or Timeout (Apache) if legitimate requests need more time.
- 3
If this happens on keep-alive connections, adjust the keep-alive timeout settings or ensure your client sends requests promptly after opening a connection.
Monitor for HTTP 408 errors
Frequent 408 errors suggest your server's timeout is too aggressive or clients have connectivity issues. Uptrack tracks response codes over time so you can spot patterns and adjust timeouts.
Catch HTTP errors before your users do
20 monitors free — 10 at 30s, 10 at 1min. No credit card required.
Start Monitoring Free