SiteError.comYour friendly guide to HTTP status codes
Status CodesBlog
  1. Home
  2. AWS ELB
  3. 460 Client Closed Connection

460 Client Closed Connection

📴
460
Client Closed Connection

Example HTTP Response

HTTP Response
HTTP/1.1 460 Client Closed Connection
Common Causes
  • Client timeout set shorter than backend processing time
  • User navigated away from page before response loaded
  • Mobile app terminated while request was in flight
  • Network interruption on client side
  • Client explicitly closed connection (browser stop button)
  • Impatient client or aggressive timeout settings
  • Slow backend causing client to give up
Technical Details

What does this mean?

You hung up too soon! Like calling tech support and then getting impatient and hanging up before they could help. The load balancer had your answer ready, but you'd already left the building!

Technical Definition

The client closed the TCP connection to the Elastic Load Balancer before the load balancer could send a response.

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(460).json({
    error: 'Client Closed Connection',
    message: 'Your error message here'
  });
});

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

http.createServer((req, res) => {
  res.writeHead(460, { 'Content-Type': 'application/json' });
  res.end(JSON.stringify({
    error: 'Client Closed Connection',
    message: 'Your error message here'
  }));
}).listen(3000);
Related Status Codes
⏰408Request Timeout📞499Client Closed Request⌛504Gateway Timeout

460 Client Closed Connection FAQ

What causes a 460 Client Closed Connection error?

Client timeout set shorter than backend processing time. User navigated away from page before response loaded. Mobile app terminated while request was in flight. Network interruption on client side. Client explicitly closed connection (browser stop button). Impatient client or aggressive timeout settings. Slow backend causing client to give up.

527 Railgun Error463 Too Many IPs in X-Forwarded-For

Popular Status Codes

  • 200 OK
  • 301 Moved Permanently
  • 302 Found
  • 400 Bad Request
  • 401 Unauthorized
  • 403 Forbidden
  • 404 Not Found
  • 500 Internal Server Error
  • 502 Bad Gateway
  • 503 Service Unavailable

Compare Codes

  • 401 vs 403
  • 301 vs 302
  • 404 vs 410
  • 500 vs 502
  • Compare any codes →

Categories

  • Informational
  • Success
  • Redirection
  • Client Error
  • Server Error
  • NGINX
  • Cloudflare
  • AWS ELB
  • Microsoft IIS

Tools

  • Cheat Sheet
  • Status Code Quiz
  • URL Checker
  • API Playground
  • Blog

© 2026 SiteError.com. All rights reserved.