Add ability to define request header to use as rate limiting key#4005
Merged
timfrazee merged 1 commit intodocker/digital-oceanfrom Mar 19, 2026
Merged
Add ability to define request header to use as rate limiting key#4005timfrazee merged 1 commit intodocker/digital-oceanfrom
timfrazee merged 1 commit intodocker/digital-oceanfrom
Conversation
Addresses an issue where proxies using non-standard forwarding headers were being rate limited on the proxy's IP
timfrazee
force-pushed
the
tf/dumb-do-header
branch
from
7fda61c to
fe1df84
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
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.
Adds ability to define
PROXY_CLIENT_IP_HEADERenv-var to define header to use as rate limiting key.Addresses an issue where proxies using non-standard forwarding headers were being rate limited on the proxy's IP