Repository navigation
Conversation
Apply the existing API rate-limit policy to auth endpoints so repeated login and logout requests receive the standard throttling response.
Rate-limit authentication routes
coder13
marked this pull request as ready for review
July 14, 2026 03:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Promotes the verified dev candidate containing #240 to master.
Included change
The authentication router now uses the established IP-based request limit, with a regression test confirming the standard 429 response.
User impact
Normal authentication remains unchanged within the configured request budget. No user-facing feature or email-related behavior changes.
Verification
The dev integration run passed server and client tests, full-stack Cypress smoke, production configuration checks, and CodeQL.