close request

Dk Jack dnj0496 at
Tue May 24 15:04:16 UTC 2022

I am noticing this with our modules. Although, we do not do not message
with any nginx reference counting etc.
At most, we are sending 403-forbidden for some requests. Could you suggest
some ways about debugging this?


This alert means that request reference counting is incorrect, and
this is serious enough to investigate as soon as possible.
Depending on various other factors, this can also result in socket
leaks, segmentation faults, or even remote code execution.

If you are seeing this with standard modules, please provide more
details. Ideally - steps how to reproduce this, though
configuration and debug logs of a particular request should be
enough. If you are seeing this with your own or 3rd party
modules, likely this indicate a bug in these modules.

Maxim Dounin
nginx-devel mailing list -- nginx-devel at
To unsubscribe send an email to nginx-devel-leave at

> Hi,
> What is the significance of this alert in ngx_http_close_request
>     if (r->count == 0) {
>         ngx_log_error(NGX_LOG_ALERT, c->log, 0, "http request count is
> zero");
>     }
> I am seeing this alert in my logs in some cases.
> Dk.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the nginx-devel mailing list