📴
460
Client Closed Connection
Example HTTP Response
HTTP Response
HTTP/1.1 460 Client Closed ConnectionCommon 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