Adds support for retrieving the IP address from the X-Forwarded-For header, for Access/Rate Limit rules #1488
Conversation
This file contains 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.
Description of the Change
Adds support to
New-PodeLimitIPComponentso it can can retrieve the IP address from theX-Forwarded-Forheader - useful for IIS, or any other proxy you're site might be running behind.You'll need to specify
-Location 'XForwardedFor', otherwise it'll use the Remote Address IP by default.When using the XFF header, Pode will use the leftmost IP by default - typically the originating client IP. You can also specify the rightmost, or all IPs, if required.
Related Issue
Resolves #1375
Examples