-
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
Limitation isn't applied on specific endpoint #46
Comments
Also, if i use */account/ActivateUser works, why? |
I´ve got the exact same scenario and also tried several endpoint definitions for my route /api/test: It will only work if the endpoint is defined with an asterisk. |
i think if your url is
|
The Wildcard match issues are fixed here: #63 |
Hi Stefan,
This is my appsettings.json
"IpRateLimiting": { "EnableEndpointRateLimiting": true, "StackBlockedRequests": true, "RealIpHeader": "X-Real-IP", "ClientIdHeader": "X-ClientId", "HttpStatusCode": 429, //"IpWhitelist": [ "127.0.0.1", "::1/10", "192.168.0.0/24" ], //"EndpointWhitelist": [ "get:/api/license", "*:/api/status" ], //"ClientWhitelist": [ "dev-id-1", "dev-id-2" ], "GeneralRules": [ { "Endpoint": "*:api/account/ActivateUser", "Period": "20m", "Limit": 1 } ] }
And this is the route that i'm calling from my angular spa
http://localhost:59323/api/account/ActivateUser
The limitation isn't applied. On the other side, if i'm using :
"Endpoint": "*",
everything works O.KAny idea? Thanks
The text was updated successfully, but these errors were encountered: