Welcome! Log In Create A New Profile


limit_req and @named locations

September 24, 2013 09:12AM
Hi list

I am experiencing some problems with a rate-limiting setup.

I have a "global" limit_req declared in my http block.

I also have additional limit_req declarations in various locations, both @named and unnamed, to provide proper protection to different backend endpoints.

It seems that additional limit_req is working fine in unnamed locations, but being ignored in @named locations.

I've linked to an example config exhibiting the problem:

If I remove the limit_req in the http block, the @dynamic limit_req works perfectly. If I enable limit_req in the http block, the @dynamic limit_req is ignored. In both cases, the limit_req in the unnamed location works perfectly!

Am I approaching this in the wrong way? How can I make limit_req work properly in the @dynamic location?



limit_req and @named locations

robwSeptember 24, 2013 09:12AM

Re: limit_req and @named locations

Maxim DouninSeptember 24, 2013 10:40AM

Re: limit_req and @named locations

robwSeptember 24, 2013 03:23PM

Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 104
Record Number of Users: 5 on August 04, 2015
Record Number of Guests: 244 on October 02, 2015
Powered by nginx    Powered by FreeBSD    PHP Powered    Powered by Percona     ipv6 ready