-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
[fix] faucet new rate limiter #20591
[fix] faucet new rate limiter #20591
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
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.
Thanks @stefan-mysten, note that we don't need to enforce per-IP rate limits at the faucet level, because there is a load balancer in front of it that already does that, but we do need to fix the previously broken middleware.
Thanks. Set up a global rate limiter for all requests, similarly to what we had before. I think this should work. |
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.
👍
ae2edf1
to
7e88bdb
Compare
Description
Previous rate limiter is likely broken. This uses a better one with a per ip address strategy.
Test plan
How did you test the new or updated feature?
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.