limit_conn not working

[Abilio Marques]

For me the documentation reads in a way in which a connection with
keep-alive that already received one request satisfies those two conditions:
- It has a request processed by the server. (processed is past tense, which
is true after the first one was made)
- The whole request has already been read.

While the actual behavior is: it has a request "being" processed by the
server and the whole request header has already been read. Once the request
is completely processed it doesn't count anymore.



On Tue, Dec 19, 2017 at 4:37 PM, Maxim Dounin <mdounin at mdounin.ru> wrote:

> Hello!
>
> On Tue, Dec 19, 2017 at 03:29:22PM +0100, Abilio Marques wrote:
>
> > I imagined to be something like that, but this is not obvious from the
> > documentation. Is there a way to clarify it for future readers?
>
> The documentation already says
> (http://nginx.org/en/docs/http/ngx_http_limit_conn_module.html):
>
> : Not all connections are counted. A connection is counted only if
> : it has a request processed by the server and the whole request
> : header has already been read.
>
> in an attempt to clarify things.  This is more or less identical
> to what I wrote.  The difference is recommendations on how to
> better trigger the limit, but I doubt such recommendations should
> be in the documentation.
>
> --
> Maxim Dounin
> http://mdounin.ru/
> _______________________________________________
> 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/20171219/b5565c4f/attachment.html>