Skip to content

460 Client Closed Connection (Load Balancer)

AWS load balancer code logged when the client closed the connection before the load balancer could respond.

Status

HTTP/1.1 460 Client Closed Connection (Load Balancer)

Details

  • Category: 4xx
  • Status: Unofficial (AWS Elastic Load Balancing). Not registered with IANA. A server, framework, or CDN convention.
  • Specification: none, not defined by any RFC
  • Cacheable: Not cacheable
  • Response body: Must not be sent
  • Retry: Safe to retry

An AWS Application Load Balancer records 460 when a client disconnects before the response is sent. The request may have been processed normally by the target; the client simply went away first.

It is a logging artefact rather than something a client receives, and it usually points at a client-side timeout shorter than the backend's processing time.

Common causes

  • A client timeout fired before the backend finished.
  • A user navigated away or cancelled the request.
  • A mobile client lost connectivity mid-request.

How to fix it

As the client

  • Raise client timeouts to exceed realistic backend processing time.
  • Cancel deliberately rather than letting timeouts fire, so retries are intentional.

As the server

  • Reduce backend latency, or switch long operations to an asynchronous pattern returning 202.
  • Compare the 460 rate with backend latency percentiles to confirm the client timeout theory.

Examples

A client that disconnected before the load balancer replied

Log

(ALB access log)
460 - - "GET https://api.example.com/slow-report HTTP/1.1"

See also