499 Client Closed Request

499

Client Closed Request

Example HTTP Response

HTTP Response

HTTP/1.1 499 Client Closed Request

Common Causes

User navigated away from page before response loaded
Client timeout exceeded server processing time
Network interruption or connection reset
User hit stop/refresh during slow request
Mobile app killed while request in flight
Impatient client closed connection

Technical Details

What does this mean?

Hello? Anyone there? You hung up before we could answer! Like calling customer service and rage-quitting before they pick up. We have your answer ready but you've already left!

Technical Definition

The client closed the connection before nginx could send a response. This code appears only in nginx logs and is never actually sent to the client.

Code Snippets

Ready-to-use code for returning this HTTP status in your application:

Node.js

// Express.js
app.get('/example', (req, res) => {
  res.status(499).json({
    error: 'Client Closed Request',
    message: 'Your error message here'
  });
});

// Native HTTP
const http = require('http');

http.createServer((req, res) => {
  res.writeHead(499, { 'Content-Type': 'application/json' });
  res.end(JSON.stringify({
    error: 'Client Closed Request',
    message: 'Your error message here'
  }));
}).listen(3000);

From the Blog

Understanding NGINX 499 Client Closed Request: When Your Users Give Up First
A deep dive into NGINX's 499 status code — what it means when the client hangs up before the server can respond, and how to use it as a leading indicator of problems.
10 min read

Related Status Codes

⏰408Request Timeout ⌛504Gateway Timeout