← All status codes4xx – Client Error

HTTP 460 – Client Closed Connection

(AWS ELB) The client closed the connection to the load balancer before the idle timeout elapsed, so no response header was received.

Common use case

Shows up in AWS Elastic Load Balancer access logs when a client (often a mobile app on a flaky connection) disconnects before the backend can respond.

History

An AWS-specific extension used only in ELB/ALB access logs, not part of any official HTTP specification.

Did you know?

You will never see this code in a browser - it exists purely as a diagnostic marker inside AWS's own logging, not as something sent over the wire to a client.

Other 4xx codes

400Bad Request401Unauthorized402Payment Required403Forbidden404Not Found405Method Not Allowed406Not Acceptable407Proxy Authentication Required408Request Timeout409Conflict410Gone411Length Required412Precondition Failed413Content Too Large414URI Too Long415Unsupported Media Type416Range Not Satisfiable417Expectation Failed418I'm a teapot422Unprocessable Content425Too Early426Upgrade Required428Precondition Required429Too Many Requests430Shopify Security Rejection431Request Header Fields Too Large444No Response451Unavailable For Legal Reasons463Malformed X-Forwarded-For Header464Incompatible Protocol Versions494Request Header Too Large495SSL Certificate Error496SSL Certificate Required497HTTP Request Sent To HTTPS Port499Client Closed Request