Forwarding headers fixes/improvements #338
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.
This branch started with a fix for #315.
webmachine_request:get_peer
now returns the earliest non-private IP, which is the one closest to the client, andwebmachine_request:get_sock
returns the latest non-private IP, which is the one closest to the server.While making the first change, I noticed that IPv6 wasn't well-supported. Localhost, link-local, and private v4 IPs translated to v6 IPs are now treated as private by
get_peer
andget_sock
.Finally, support is added for the standardized
Forwarded
header.X-Forwarded-For
is checked only if no answer was found inForwarded
.This is all implemented based on reading specs and other guides. I don't have a proper setup to test the behaviors of real-world proxies.