limit_req_zone limit by location/proxy

Maxim Dounin mdounin at
Wed Nov 13 13:40:01 UTC 2013


On Wed, Nov 13, 2013 at 07:17:36AM -0600, Justin Deltener wrote:


> current requests..which is what i'm attempting to do) Using a burst of 6, i
> would expect a request of 8 in one second would have 4 at full speed, 2
> delayed and 2 dropped but it seems that's where i'm horribly wrong. You
> said "As long as rate is set to 4r/s, it's enough to do two requests with
> less than 250ms between them to trigger "delaying request message". I'm
> confused, why would 4r/s not allow 4 requests per second at full speed??
> Isn't that the entire point.

Two request with 100ms between them means that requests are coming 
at a 10 requests per second rate.  That is, second request have to 
be delayed.

Note that specifying rate of 4 r/s doesn't imply 1-second 
measurement granularity.  Much like 60 km/h speed limit doesn't 
imply that you have to drive for an hour before you'll reach a 

Maxim Dounin

More information about the nginx mailing list