-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
feat: Improve default rateLimit options #8506
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
Conversation
I will reformat the title to use the proper commit message syntax. |
Thanks for opening this pull request! |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## alpha #8506 +/- ##
==========================================
+ Coverage 94.19% 94.32% +0.12%
==========================================
Files 186 183 -3
Lines 14819 14515 -304
==========================================
- Hits 13959 13691 -268
+ Misses 860 824 -36 ☔ View full report in Codecov by Sentry. |
errorResponseMessage: 'Too many requests', | ||
}, | ||
{ | ||
requestPath: '/login|verifyPassword', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'/login|verifyPassword'
This looks strange, is that regex? If so, shouldn't it be '/(login|verifyPassword)'?
This is a breaking change, so we can merge this earliest in Nov/Dec 2023 for Parse Server 7. |
Closing, see #8489 (comment) |
Pull Request
Issue
Currently, there are no default rate limits. We should at protect login and signup endpoints from being spammed.
Closes: #8489
Approach
Adds more restrictive default rate limits
Tasks