use different HTTP headers other than X-Forwarded-For #94
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.
Dear all,
our web server is behind a proxy cascade. So the X-Forwarded-For header only delivers the ip address of the front end proxy but the ip address is in a different header (for example X-Remote-Client-IP). Changing the names is not possible for technical reasons outside my influence.
To deal with this I integrated a new option suhosin.log.remote-addr-header (with "HTTP_X_FORWARDED_FOR" as default). This option is only used if suhosin.log.remote-addr-header is enabled.
I decided to use the php style to reference headers. So you have to prepend HTTP_ and translate hyphens to underscores.
I also integrated a documented entry in the suhosin.ini and added some test scripts.
with kind regards,
Joerg