-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat(node): Implement category based rate limiting #3435
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
12b0628 to
2af71f0
Compare
size-limit report
|
kamilogorek
left a comment
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.
Perfect copy-paste skills 🥰
HazAT
left a comment
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.
I think the only thing missing is bogus test cases where the header is malformed or not there.
Also what about an unknown category?
2af71f0 to
fa33eb1
Compare
fa33eb1 to
7e3e604
Compare
HazAT
left a comment
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.
Do we really need to test both http and https and have a lot of duplicated tests? I think for this PR that's not necessary.
Add Category rate limiting based on SentryRequestType
7e3e604 to
c9978cd
Compare
This PR:
event,transaction,sessionX-Sentry-Rate-Limitsheader -> all categories are rate limited