[IE] Re: limit_conn not working

Jason Whittington Jason.Whittington at equifax.com
Tue Dec 19 18:12:12 UTC 2017

If you have a github account you can fork the nginx wiki troubleshooting and send them a pull request ☺

https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/   Look for “Edit this page” in the rightmost column.


From: nginx [mailto:nginx-bounces at nginx.org] On Behalf Of Abilio Marques
Sent: Tuesday, December 19, 2017 8:29 AM
To: nginx at nginx.org
Subject: [IE] Re: limit_conn not working


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?

On Tue, Dec 19, 2017 at 3:26 PM, Maxim Dounin <mdounin at mdounin.ru<mailto:mdounin at mdounin.ru>> wrote:

On Tue, Dec 19, 2017 at 06:36:00AM +0100, Abilio Marques wrote:

> limit_conn is not working for me. I set up a test in nodejs, I'm doing GET
> requests to http://localhost/, they are coming from different connections
> (different origin ports), and all the connections are still open until the
> very end, still, no response other than 200 is received. I double check
> with wireshark.
> What am I missing??
> Minimal configuration I can reproduce it with: https://paste.ngx.cc/70
> Source code for the test: https://paste.ngx.cc/6f
The limit_conn limit only limits connections with active requests.
Moreover, it only applies after reading request headers - as nginx
needs to know requested host and URI to check limits appropriate
for particular server and location blocks.

As a result, it is almost impossible to trigger limit_conn by
requests to small static files.  To trigger limit_conn, consider
testing it with files large enough to fill up socket buffers,
and/or with proxying.

Maxim Dounin
nginx mailing list
nginx at nginx.org<mailto:nginx at nginx.org>

This message contains proprietary information from Equifax which may be confidential. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e-mail postmaster at equifax.com. Equifax® is a registered trademark of Equifax Inc. All rights reserved.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20171219/3c841db5/attachment.html>

More information about the nginx mailing list