in search of the complete 444

[Moshe Katz]

I found the same question asked on StackOverflow a few years ago:
https://stackoverflow.com/questions/41421111/http-444-no-response-instead-of-404-403-error-pages


The accepted answer says to do it this way:

```
error_page 400 =444 @blackhole;

location @blackhole {
    return 444;
}
```

They key that you missed is the "=444" in the error_page directive. It
seems like you need BOTH that and the `return 444` in the location block.

Moshe



On Mon, Jun 8, 2020 at 4:35 PM Jeffrey 'jf' Lim <jfs.world at gmail.com> wrote:

> I've been trying and scratching my head over this for some time now.
> I've always set up a default server to return 444, but I've not been
> able to make it do the 444 *always*. If I get an invalid response,
> nginx "skips" the 444 to return 400 instead. I'd rather nginx do the
> 444, and not return 400.
>
> I've searched and tried various things (like setting "error_page 400"
> to some location, and then returning 444 for that location), but I
> have not found anything that really works. Is there just no way to
> have a "complete" 444 response? What will it take to do this?
>
> thanks,
> -jf
>
> --
> He who settles on the idea of the intelligent man as a static entity
> only shows himself to be a fool.
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20200608/f3cf3737/attachment.htm>