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
Add DDPRateLimit to all exposed client methods #1267
Comments
First task would be to delineate the methods (pretty much anything public client facing) and determine where the upper limit of what a reasonable use case would be. |
FYI, I added some initial rate limiting for accounts and email notification methods in #1282. |
Closing - insufficient details. Will be handled as part of next architecture as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This ticket is in reference to #344.
For DoS protection we should wrap all client facing methods with DDPRateLimit.
(More detailed actions items to come) Might/will need to break this ticket down even further.
The text was updated successfully, but these errors were encountered: