feat: RATE_LIMITING env var and config docs#75
Merged
GraysonCAdams merged 2 commits intomainfrom Mar 4, 2026
Merged
Conversation
Rate limiting is now opt-in via RATE_LIMITING=true. When disabled (the default), checkRateLimit always allows requests, the in-memory store is never populated, and the cleanup interval doesn't start. This covers both the hook-level and route-level rate limit checks.
6c12421 to
d0608bf
Compare
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
RATE_LIMITINGenv var (defaultfalse) — rate limiting is now opt-in viaRATE_LIMITING=truecheckRateLimitalways allows requests, the in-memory store is never populated, and the cleanup interval doesn't start — covers both hook-level and route-level checks (auth join endpoint)RATE_LIMITING,VERBOSE_REQUESTS,ADDRESS_HEADER, andXFF_DEPTHin the configuration referenceTest plan
RATE_LIMITINGset — no rate limiting appliedRATE_LIMITING=trueenables rate limiting as before