This repository was archived by the owner on Apr 11, 2021. It is now read-only.
Include remote address in request header#19
Open
TheHackerDev wants to merge 1 commit intoyanc0:masterfrom
Open
Include remote address in request header#19TheHackerDev wants to merge 1 commit intoyanc0:masterfrom
TheHackerDev wants to merge 1 commit intoyanc0:masterfrom
Conversation
Owner
|
Thanks Aaron ! |
Contributor
Author
|
No problem, Yann! Cheers, |
Owner
|
Hi Aaron, I've just fetch your PR locally and bound Beeping on an IPv6 address. It almost works, I get the header but with too much surround brackets:
There is no need to add brackets when you split IP:PORT, they are apparently already there in the The fix could be: Here are my tests on Debian: Thanks Aaron ! |
Merged
This file contains hidden or 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Includes the remote address in the request, following RFC 7239, section 4.
This is not going to be exact for every case, because
http.Request.RemoteAddrhas no defined format (see https://golang.org/src/net/http/request.go#L260). However,http.Serversets the address toIP:port, so it is safe to go with that.NOTE: I was unable to check this with an IPv6 source address. Please do so before merging, to confirm that IPv6 source addresses get transformed to look like the following header:
Forwarded: For="[2001:db8:cafe::17]"I was mostly unsure as to whether the
http.Serverset theremoteAddrvalue for IPv6 addresses with square brackets or not. The assumption in the code's logic right now is that it does not.Cheers,
Aaron (insp3ctre)