HTTP 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
Start free, or choose a plan, for 30-second monitoring and alert confirmation.
from $3/mo · 30-day money-back guarantee
Other HTTP status codes
- HTTP 409 Conflict
- HTTP 410 Gone
- HTTP 405 Method Not Allowed
- HTTP 404 Not Found
- HTTP 403 Forbidden
- HTTP 413 Payload Too Large
- HTTP 401 Unauthorized
- HTTP 415 Unsupported Media Type
- HTTP 400 Bad Request
- HTTP 422 Unprocessable Entity
- HTTP 429 Too Many Requests
- HTTP 451 Unavailable For Legal Reasons
- HTTP 500 Internal Server Error
- HTTP 502 Bad Gateway
- HTTP 503 Service Unavailable
- HTTP 504 Gateway Timeout
- HTTP 304 Not Modified
- HTTP 302 Found
- HTTP 301 Moved Permanently
- HTTP 520 Web Server Returns Unknown Error
- HTTP 522 Connection Timed Out
- HTTP 204 No Content
- HTTP 201 Created
- HTTP 200 OK