-
Notifications
You must be signed in to change notification settings - Fork 449
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How do you create dynamic URL (parameter) rules? #29
Comments
Yes that should work I think, the latest version has a wildcard implementation #25 |
Not sure this answers the question. I think what he is asking for the specifics of an Id param. Like his example. Or are you saying to do that, * is the same thing as {id}. I am testing this on latest version and also cannot get a param to be recognized. |
Is there a way to use the wildcard as part of the rate limit rule? So in the above example what if you want to rate limit any calls to |
I think I am asking for the same as #13 which is the inverse of what @kspearrin is asking for. |
Did this ever get implemented? Because I've recently implemented this and doesn't appear to work. |
Ok I found out the issue. I had several. First I'm just using ClientRateLimiting but looks like it would apply to IPRateLimiting as well.
My scenario had an Endpoint: "post:/api/clients//dosomething/". It was able to match on that when calling /api/clients/v1/dosomehting/100. Hope this helps someone out as I just spent the last several hours pulling what little hair I have left out. :) |
Hi! I hope this is useful for someone! |
Check this out: #63 |
How do you create dynamic URL rules? For example, I have a URL:
POST example.com/user/{id}/something
where {id} changes per user. I'd like to limit it to 1 call per second per user id.
Should the rule look like this or what?
I couldn't find anything in the docs. Thanks!
The text was updated successfully, but these errors were encountered: