Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a method to expose the proxy protocol destination address. #7

Merged
merged 2 commits into from
Feb 11, 2019

Conversation

tomwilkie
Copy link
Contributor

@tomwilkie tomwilkie commented Feb 15, 2017

Alternatively, we could expose it as part of LocalAddr(), similar to RemoteAddr(). WDYT?

@pquerna
Copy link

pquerna commented Apr 25, 2017

This should be conn.LocalAddr(), since thats what the proxy protocol line is telling us IMO

tomwilkie and others added 2 commits September 20, 2018 09:09
Also extended the existing SourceCheck() mechanism to govern both
remote and local addresses.
@bboreham
Copy link
Contributor

Rebased and updated in line with your feedback. I left the two commits so it's clear who did what.

@bboreham
Copy link
Contributor

bboreham commented Feb 8, 2019

@armon @pquerna any further thoughts?

@armon
Copy link
Owner

armon commented Feb 11, 2019

LGTM!

@armon armon merged commit 68259f7 into armon:master Feb 11, 2019
nathanejohnson added a commit to nathanejohnson/go-proxyproto that referenced this pull request Oct 18, 2020
This should allow users to simulate the functionality with LocalAddr()
that changed with armon#7 .
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants