Support Regex in the Path endpoints about aspnetcoreratelimit HOT 7 CLOSED

from aspnetcoreratelimit.

Hello,

As a workaround, until I find some time to implement regex you can whitelist "get:/api/values/Search" and rate limit "get:/api/values/".

from aspnetcoreratelimit.

I believe Controller and ActionMethods attributes are a must. This way, you have right in your controller the endpoint specific rules. This prevent mistakes when an api route is modified but the limit configuration is not updated to reflect the changes.

In my opinion, those attributes should be heavily inspired by the ASP.Net Core ResponseCache attributes.

The attributes should also support a way of applying the limit per action-method, per route (taking into account the route parameters), and even maybe by url (taking into account the query parameters).

from aspnetcoreratelimit.

Would you hardcode IPs and client API keys in those attributes?

from aspnetcoreratelimit.

Have IPs, and client API keys loaded from a configuration like before, attribute-based rules as an option, or just like before, load ratelimit rules from a file.

from aspnetcoreratelimit.

Like @ledouxpl I rely a lot on route parameters. I am currently implementing the middleware but just came across an issue, where I have to rate limit an endpoint that uses a route parameter. Not having the option of wildcards in endpoint paths is a blocking restriction.

from aspnetcoreratelimit.

check this out #63

from aspnetcoreratelimit.