Re: limit_req_zone: How to apply only to some requests containing some string in the URL?
On Fri, Oct 25, 2013 at 07:07:20PM -0400, Brian08275660 wrote:
Hi there,
~*(.*)X
I think that the first two characters mean match anycase, then the (.*)
would mean any quantity of characters and the X would mean that specific
letter.
Am I right?
Yes.
But unless you're going to do something with the bit before the X,
then in the context of a map{}, it is equivalent to ~*X, since all you
care about is whether it matches.
It will just as easily match x123 or 123x123.
f
--
Francis Dalyfran...@daoine.org
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Re: limit_req_zone: How to apply only to some requests containing some string in the URL?
Oh, ok. Then it is similar to REGEX in Java. Well, then I think I have a nice and elegant solution, Thanks! Posted at Nginx Forum: http://forum.nginx.org/read.php?2,244015,244149#msg-244149 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
Re: limit_req_zone: How to apply only to some requests containing some string in the URL?
Hi,
you could use a map that matches all cases to empty string and default
value as non-empty
map $arg_capacity $my_default_key{~*([2-9]|10)X ; default
$http_x_forwarded_for;}
If it matches 2X to 10X, $my_default_key will be empty.
Cheers
Jader H. Silva
2013/10/25 Brian08275660 nginx-fo...@nginx.us
Hi Francis,
Now I need to create a limit that acts if the parameter (capacity) is
empty (not provided). How do I do that? I can't find how to, at least not
using map.
(If provided, the other rules will evaluate it and one of them will act
according to the value).
Thanks in advanced!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,244015,244123#msg-244123
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Re: limit_req_zone: How to apply only to some requests containing some string in the URL?
Maybe ive misunderstood but cant you very simply do this by injecting a cookie on the origina req page and then have nginx match, count it and apply rates? Or maybe im comicating it... If even possible -- Payam Chychi Network Engineer / Security Specialist On Tuesday, October 22, 2013 at 8:42 PM, Brian08275660 wrote: Hi, I'm using the limit_req_zone module. I would like it to act only on some requests that have a certain string in one variable in the query string of the URL.For example, lets say that I'm providing a IP geolocation service, and that in the URL there is a query string like this: http://api.acme.com/ipgeolocation/locate?key=NANDSBFHGWHWN2Xip=146.105.11.59 I would like the rule to detect when the key parameter ends with 2X, and in such case to apply the limitation. What I really need is to give NGINX a secret message. The key parameter would end in 01X, 02X, 03X (etc). This would indicate Nginx the limitation of queries per minute, and Nginx would apply a different rate for each request, depending on the message. Is there a way to do that? Thanks in advance! Posted at Nginx Forum: http://forum.nginx.org/read.php?2,244015,244015#msg-244015 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
Re: limit_req_zone: How to apply only to some requests containing some string in the URL?
Hi Jader,
Thanks a lot, that looks like a nice solution!
I barely know how to build regex expressions, and I'm too lazy to learn just
right now. Just a final question: Actually they will send me any value from
2X to 25X, but that could even increase to more than 25. I would like a
simpler and more open REGEX, something like:
If it is something that includes an X
I will use it as this:
map $arg_capacity $my_default_key{ If it is something that includes an X
; default $http_x_forwarded_for;}
Simple as that. This would catch any case, from 2X to 10X. Actually
it would catch even illegal values. But that is not a problem for me, cause
in my java code that follows Nginx I'm validating the value they send me
anyway, so I don't mind if they send me a value like -1X because my app
would return an error status code and force them to send me a valid value
anyway. The important thing is that Nginx should apply the limit if the
received value is not empty, and asking if it contains an X covers that
boolean question.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,244015,244129#msg-244129
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Re: limit_req_zone: How to apply only to some requests containing some string in the URL?
Hi Payam, I dont have that option. My users are not using real browsers, but objects that model an HTTP client. Probably these object can't inject cookies. And I don't want to ask them to so so, it would make things more complex to them, whereas including an extra parameter in the query string is a piece of cake. Thanks anyway for the idea! Posted at Nginx Forum: http://forum.nginx.org/read.php?2,244015,244130#msg-244130 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
Re: limit_req_zone: How to apply only to some requests containing some string in the URL?
I read some information about REGEX and think I found the way to express X or x, preceded with something before: ~*(.*)X I think that the first two characters mean match anycase, then the (.*) would mean any quantity of characters and the X would mean that specific letter. Am I right? Posted at Nginx Forum: http://forum.nginx.org/read.php?2,244015,244136#msg-244136 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
Re: limit_req_zone: How to apply only to some requests containing some string in the URL?
On Tue, Oct 22, 2013 at 11:42:35PM -0400, Brian08275660 wrote: Hi there, I'm using the limit_req_zone module. I would like it to act only on some requests that have a certain string in one variable in the query string of the URL. http://api.acme.com/ipgeolocation/locate?key=NANDSBFHGWHWN2Xip=146.105.11.59 I would like the rule to detect when the key parameter ends with 2X, and in such case to apply the limitation. http://nginx.org/r/limit_req_zone See $variable. Use, for example, map to make your variable have a value when you want the limit to apply, and be empty when you don't. What I really need is to give NGINX a secret message. The key parameter would end in 01X, 02X, 03X (etc). This would indicate Nginx the limitation of queries per minute, and Nginx would apply a different rate for each request, depending on the message. For that, I think you'd need a different limit_req zone for each rate. After you've got the first part working, it shouldn't be too hard to set up a test system to see if you can get this part to work too. f -- Francis Dalyfran...@daoine.org ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
Re: limit_req_zone: How to apply only to some requests containing some string in the URL?
Thanks a lot Francis! Now I just have to learn how to use the custom variables and the map directive. I haven't ever used them before, never needed them. By the way, it will be easier than what I thought. I decided to ask my users to add an extra parameter, something like capacity=3X instead of hiding some characters in the key that would indicate what to do. So at least I wont have to make a lot of effort with the regular expressions, the parameter will be very clear. My logic will chech its value and apply the respective limit. Its interesting how weird is the configuration of Nginx. No XML tags, but weird directives that are not really straightforward. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,244015,244049#msg-244049 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
