-
Notifications
You must be signed in to change notification settings - Fork 55
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
Throttle on only a single route #1900
Comments
@Canoir it was your company's concern too, right? |
Okay, I think I see the request here. Instead of being forced to use the I think the In the As for the initial "How can I implement this?", so long as there's a config object passed to the |
I agree with you and about the name: config , I think that is great too, our need is exactly what you said, but your other answer make me a bigger question, what will happen if we pass ttl: 0 and limit 0 to global config? I mean if the guard only passes cause of 0 then there is a little bit shitty but solution to our problem even now, right? |
The idea I suggested was just to make sure that there was a default config so that the |
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
My challenge is how to apply throttling to a specific route without setting up a global throttle. My concern arises from the necessity to log every single request from every single user (in memory) when establishing a global throttling system, to ascertain whether the new request necessitates throttling. How can I accomplish this?
Describe the solution you'd like
Globally config it like:
and use it like this on the route:
Notes:
Teachability, documentation, adoption, migration strategy
No response
What is the motivation / use case for changing the behavior?
For more customizations and more control for throttling and saving more space.
The text was updated successfully, but these errors were encountered: