Safer/trustable extraction of real ip from request #1478
Merged
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.
IP address extraction using HTTP header requires additional care. Otherwise attackers might have a chance to deceive wrong ip address.
I fixed this problem.
See also: #855
I wrote detailed doc in labstack/echox#134, tl; dr:
Especially about XFF header parsing, see implementations from other players:
Another note about XFF header:
,
without whitespace (e.g.: http-party/node-http-proxy)