HTTP 408 Request Timeout — Causes, Fix & Server Configuration

When to Return 408

Typically sent by the server infrastructure (nginx, load balancers) rather than application code. Implement in application code when processing has a maximum time budget and the client's connection stalled.

Common Causes

• Client connection dropped mid-request
• Slow network causing request body to arrive slowly
• Large file upload stalled
• Client opened connection but never sent headers

HTTP Response Example

HTTP/1.1 408 Request Timeout
Connection: close
Content-Type: application/json

{"error": "Request Timeout"}

Code Examples

// Usually set by server config, not app code.
// In Express, configure the underlying http server:
const server = app.listen(3000)
server.setTimeout(30_000) // 30 second request timeout

// Or in middleware:
app.use((req, res, next) => {
  req.setTimeout(30_000, () => {
    res.status(408).json({ error: 'Request Timeout' })
  })
  next()
})

// next.config.ts — server actions and API routes have no default timeout.
// Set per-route with the maxDuration export:
export const maxDuration = 30 // 30 seconds (Vercel / Node.js runtime)

Related Status Codes