DevArbor
4xx Client Error

408 Request Timeout

What it means

The server did not receive a complete request within the time it was prepared to wait. The server decided to close the connection rather than continue waiting. The client may repeat the request without modifications.

Site Visitor

What can I do?

  • Check your internet connection and try again.
  • If on a slow connection, wait for the connection to stabilize.
  • If the problem persists after retrying, contact the site owner.
Developer

How to debug & fix

  1. Set appropriate timeout values — not too aggressive for legitimate slow connections
  2. Send Connection: close in the 408 response to signal connection close
  3. Consider if clients might legitimately need more time (large uploads)
  4. Set per-route timeouts appropriate to the operation (shorter for search, longer for uploads).

Code Example

Node.js / Express
// Configure request timeout in Express
app.use((req, res, next) => {
  req.setTimeout(5000, () => {
    res.status(408).json({ error: 'Request Timeout' });
  });
  next();
});

Related Status Codes

504 Gateway Timeout 503 Service Unavailable

How HTTP Status Codes Work

Every HTTP response carries a three-digit status code that tells the client — browser, API consumer, or search-engine crawler — exactly what happened. The first digit defines the class: 1xx informational (request in progress), 2xx success, 3xx redirection, 4xx client error (bad request, missing auth, not found), and 5xx server failure.

Status codes are standardised in RFC 9110 (HTTP Semantics, 2022). Extensions like WebDAV (RFC 4918) and rate-limit headers (RFC 6585) added codes beyond the core set. When a client receives an unrecognised code, the rule is to treat it as the generic x00 of its class.

Why the Right Code Matters

Semantically correct codes help search engines index accurately (301 passes link equity; 410 removes pages faster than 404), allow API clients to implement correct retry logic (429 + Retry-After, 503 + Retry-After), and let monitoring systems distinguish bugs (500) from load issues (503) from auth failures (401/403).

Looking up a different status code? The full reference covers all HTTP codes with causes, fix guides, and copyable code examples for Node.js and Python.

Browse the full HTTP Status Code reference →

Frequently Asked Questions

What does HTTP 408 Request Timeout mean?
The server did not receive a complete request within the time it was prepared to wait. The server decided to close the connection rather than continue waiting. The client may repeat the request without modifications.
Is HTTP 408 the visitor's fault?
HTTP 408 Request Timeout is generally a client-side error, meaning the request itself has an issue. However, many causes — such as a broken link on the site or a misconfigured redirect — are the website owner's responsibility, not the visitor's.
How do I fix HTTP 408 Request Timeout?
As a visitor: check the URL for typos, go to the homepage, or search for the content. As a developer: set appropriate timeout values — not too aggressive for legitimate slow connections.