Hello!
On Fri, Dec 01, 2017 at 06:43:36AM -0800, Gary wrote:
> Is this limiting for one connection or rate limiting for the
> entire server? I interpret this as a limit for one connection.
The request limiting can be configured in multiple ways. It is
typically configured using $binary_remot
Is this limiting for one connection or rate limiting for the entire server? I
interpret this as a limit for one connection.
I got rid of the trailing period.
https://en.wikipedia.org/wiki/Leaky_bucket
A request is one line in the access log I assume, typically a html verb like
"get". I use a
Hello!
On Fri, Dec 01, 2017 at 11:18:06AM +0800, tongshus...@migu.cn wrote:
> I configured as below:
> limit_req_zone "all" zone=all:100m rate=2000r/s;
> limit_req zone=all burst=100 nodelay;
> but when testing,I use tool to send the request at: Qps:486.1(not reach 2000)
> I got the many many 5
the nginx.conf as below:
upstream my_server {
server localhost:8095;
keepalive 2000;
}
location /private/rush2purchase/ {
limit_conn addr 20;
proxy_pass http://my_server/private/rush2purchase/;
proxy_set_header Host $host:$server_port;
rewrite_by_lua_file D:/tmp/lua/draw_r
Thank you for your answer,
I am using an old version (1.8.1).
I will try to upgrade to 1.12 and check if it solve my problem.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,277597,277616#msg-277616
___
nginx mailing list
nginx@nginx.org
http