Repository navigation
configuration by path with path_limits is not working #104
Description
Activity
Paths are not regular expressions, but just simple prefixes
In the config example, there is :
# - { path: /api, limit: 1000, period: 3600 }
Does it mean all routes begin with /api are under this limit or I am wrong?ex: http//:mysite.com/api/user ; http//:mysite.com/api/cars ; http//:mysite.com/api/whateveryouwant
EDIT:
I think I understood my issue was with 2 rules likes this
and it does not work for the api/login_check, maybe because it is in security.yaml
In the description of the issue you have
'^/api', but should just be'/api'Reacted by JulienYes thank you for your answer!
The only route what I don't understand it is not working now is the login_check (to create the JTW)I have same issue. I am using lexik JWT token generator. Default login_check route not using ratelimit
I don't understand why the limit path defined in the configuration is not working whereas it is working with annotation in the controller.
i set
path_limits: - { path: '^/api', limit: 1, period: 3600 }and nothing in the header with an /api/* url :
whereas is it working with the controller if defined for a specific one :
Do you have an idea?