- Home
- Tools
- Developer Tools
- HTTP Status Codes
- 444 No Response
444 No Response
An nginx setting that closes the connection without sending anything. The number only appears in the access log of nginx itself.
- Class
- Unofficial codes. Not in the IANA registry. These are made up by one piece of software and mean nothing outside it, but they turn up in logs and on error pages often enough.
- Used by
- nginx
What causes it
When the configuration says return 444. Administrators use it to get rid of requests they don't want to spend a response on: scanners that ask for paths that don't exist, or requests for a host name the server doesn't serve.
What to do about it
The client never sees a 444. It sees the connection close without an answer, which a browser reports as an empty response and curl as "Empty reply from server". If that happens on your own site, search the nginx configuration for return 444 and check which rule catches legitimate requests.
Not to be confused with
| 403 Forbidden | A refusal that does send a response. |
|---|---|
| 499 Client Closed Request | The other way round: the client closed the connection. |
All codes are on the list of HTTP status codes, which can be searched by number and by word.