Gateway: env-configurable rate-limit skip prefixes for shared-NAT deployments - #259
Merged
Conversation
…loyments GATEWAY_RATE_LIMIT_SKIP_PREFIXES (comma-separated path prefixes) exempts matching paths from the general per-IP limiter. Needed where many clients sit behind one NAT IP and reach the gateway through an allowlisted reverse proxy: per-IP buckets collapse into one shared bucket and a burst of legitimate clients exhausts it collectively. Default unset; behavior unchanged unless the env var is provided.
kh0pper
added a commit
that referenced
this pull request
Jul 31, 2026
GATEWAY_FUNNEL_PUBLIC_PREFIXES (comma-separated, same trailing-slash semantics as PUBLIC_FUNNEL_PREFIXES) lets a deployment expose additional public surfaces over Tailscale Funnel without patching the static list. Default unset: behavior unchanged. Entries not starting with '/' are dropped. Mirrors the GATEWAY_RATE_LIMIT_SKIP_PREFIXES pattern (#259). Co-authored-by: kh0pper <kevin.hopper@maestro.press>
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
1 participant
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.
The gateway general limiter keys per IP (200 req / 15 min). Where many clients share one NAT egress IP and arrive through an allowlisted reverse proxy, every client lands in the same bucket, and a burst of legitimate traffic 429s everyone at once (observed live: a training room of phones first-loading a public surface exhausted the shared bucket in seconds).
Adds GATEWAY_RATE_LIMIT_SKIP_PREFIXES: comma-separated extra path prefixes the general limiter skips, alongside the existing hardcoded skips. Default unset; behavior unchanged unless a deployment opts in. Auth and dashboard limiters untouched.
Verified live on the affected deployment: 300 consecutive burst requests to an exempted surface return 200; non-exempted paths keep existing limits.