Allow to log real client ip in logs when using a reverse proxy #398
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
|
Is there anything specific that is preventing this option being merged? I manually applied this patch to my server running the latest version (1.17.2) and there were no conflicts. I am getting the real IP addresses in my log now, which is awesome! |
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.
Add a new LD_LOG_X_FORWARDED_FOR environment variable allowing to manage
uWSGI log-x-forwarded-for parameter. It allows to use the ip from X-Forwarded-For header instead of REMOTE_ADDR in logs and thus to keep real client IP when using a reverse proxy.