Hello Maxim,
Interesting thing I noticed is that this alert only happens when the
received request is HTTPv2. If the received is HTTPv1.1 and with no changes
to my module, I don't see this log message. Does this suggest something?
On Tue, May 24, 2022 at 10:23 AM Maxim Dounin wrote:
> Hello!
>
Hello!
On Tue, May 24, 2022 at 08:04:16AM -0700, Dk Jack wrote:
> 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?
Maxim,
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?
Thanks.
Bhasker.
Hello!
On Mon, May 23, 2022 at 12:24:16PM -0700, Dk Jack wrote:
> 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
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.
___
nginx-devel
