Allow U&P rate limiter's config to be overridden for specific routes #12375
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does it do?
It overrides the default U&P rate limiter settings when a config is specified for the middleware at a specific route.
Why is it needed?
Currently, there is no way to change the rate limiting criteria for U&P routes on a per-route basis. You either keep the defaults or change those defaults for all routes, but you can't set specific requirements just for certain routes – eg. those that send emails.
How to test it?
Try overriding the rate limiter's config either through a direct extension of the U&P plugin or through the register function.