Skip to content
4444xx · Client errorThe client seems to have erred. RFC 9110 §15.5

HTTP 444 No Response: meaning and troubleshooting

Meaning

HTTP 444 is nginx's silent connection close, so clients see an empty reply instead of an HTTP response. Find the edge rule before retrying.

HTTP 444 is an nginx-specific action that closes the connection without sending an HTTP response. It is not in the IANA registry and has no RFC reason phrase. The nginx return directive documentation describes 444 as closing the connection, which is why curl reports an empty reply instead of a status line. A site can use it to drop a request that matches a local access rule, but another server or proxy may translate the silent close into its own error.

That translation matters to scrapers. A direct request can produce curl error 52, while the same request through Squid can produce 502 Bad Gateway. The 502 is Squid’s report that its upstream sent zero bytes. It does not prove the origin generated a standards-based 502.

Reproduce the empty reply locally

This Python 3.15.0 program performs the network action nginx uses for 444: it reads the request and closes the socket without writing bytes. It is useful for testing a client’s distinction between a status response and a transport failure.

# drop444.py
import socket

srv = socket.create_server(("127.0.0.1", 8444))
while True:
    conn, _ = srv.accept()
    conn.recv(65536)
    conn.close()
$ curl -sS -i http://127.0.0.1:8444/
curl: (52) Empty reply from server

$ curl -sS -i -x http://127.0.0.1:38128 http://127.0.0.1:8444/
HTTP/1.1 502 Bad Gateway
Server: squid/6.13
X-Squid-Error: ERR_ZERO_SIZE_OBJECT 0
Via: 1.1 lab-proxy (squid/6.13)
Connection: keep-alive

The capture used curl 8.7.1 and Squid 6.13 on loopback. The direct client received no status line at all. Squid generated a complete 502 page because it could not parse an upstream response. A client that retries every 502 may therefore repeat an nginx access-rule match indefinitely.

What 444 means at an nginx site

444 usually appears in a server or location block that has already classified the request. Operators use it for a disallowed hostname, a malformed request, a known scanner pattern or an address list. The code itself carries no reason, body or Retry-After value. Nginx access logs are the authoritative place to learn which rule ran.

Do not confuse 444 with a network outage. A closed connection from a load balancer, firewall or application can look identical to the client. Repeat the request with a harmless path, then compare the direct path and a known-good proxy. If only one URL family closes, inspect that virtual host’s rules. If every host closes, check the listener and the path between the client and the server.

444 is not a registered HTTP status. Do not write “HTTP 444” into a generic API contract unless you control both sides. Expose a registered 403 or 429 when the caller needs a machine-readable reason, and keep the silent close as an edge policy only when you accept that clients will see a transport error.

Causes and fixes

What you observe Likely layer What to change
curl error 52 and no response bytes nginx 444, a firewall or an application that closed cleanly Check the origin access log and repeat a known-good URL; treat it as a transport failure
502 with ERR_ZERO_SIZE_OBJECT through Squid The proxy received zero bytes from its upstream Inspect the upstream rule; do not assume the proxy itself is unhealthy
Only a bot User-Agent triggers the close An nginx map or WAF rule Use an honest client identity, obey the site’s terms and reduce request rate
Only one Hostname triggers it Server-name or default-server access rule Use the canonical hostname and keep SNI, Host and the URL aligned
Close follows a burst of requests Rate or connection rule at the edge Stop, wait, and implement bounded backoff instead of rotating immediately
Every request closes from one network Firewall or upstream routing issue Compare a second network and check the listener before changing the scraper

For a scraper, record the transport error separately from HTTP statuses. A retry policy that handles 502 and 503 but treats error 52 as a generic success can silently drop data. Keep the URL, method, proxy exit, TLS result and elapsed time in the log. The 403 vs 407 vs 429 guide covers registered refusals, while the 408 Request Timeout reference explains how clients report a close before headers. Do not invent an HTTP meaning for 444.

Frequently asked questions

Is 444 a real HTTP status code?
Nginx recognises it as a local return action, but it is not an IANA-registered HTTP status.
Should I retry after 444?
Stop and diagnose the rule. Repeating the same request can keep the edge rule hot.

Sources

  1. nginx documentation: return directive and non-standard 444
  2. IANA HTTP Status Code Registry

All terms, A to Z