Welcome! Log In Create A New Profile

Advanced

Re: limit_req seems to have no effect, but I would prefer it did

October 11, 2012 05:34AM
On Thursday 11 October 2012 05:17:19 zildjohn01 wrote:
> That definitely explains the behavior I was seeing. But to me, any way to
> bypass the rate limiter seems like a security hole.

Just "return 410;" is the much cheaper than the whole request limitation thing.
And it's a good reason to save the resources and don't do limitation at all in
this case.

The limit modules should be used to limit access to any resource consumption
tasks, not trivial. Limiting for "return 410;" seems pointless to me.

> Is there any way to change the phase/order of these two directives,

No, there is no way.

> or to otherwise cause rewritten requests to be rate limited?

You can try some workaround like this:

location / {
try_files /410 @410;
}

location @410 {
return 410;
}


wbr, Valentin V. Bartenev

--
http://nginx.com/support.html

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

limit_req seems to have no effect, but I would prefer it did

zildjohn01 October 09, 2012 05:20AM

Re: limit_req seems to have no effect, but I would prefer it did

VBart October 09, 2012 06:16AM

Re: limit_req seems to have no effect, but I would prefer it did

zildjohn01 October 10, 2012 09:17PM

Re: limit_req seems to have no effect, but I would prefer it did

VBart October 11, 2012 05:34AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 254
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready