We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In certain cases it might be usefuy to have the remote address on the connection state.
For example, I want to validate during handhsake process (VerifyConnection callback) that the peer certificate was issued with the remote address.
type ConnectionState struct { ... RemoteAddr Addr }
The text was updated successfully, but these errors were encountered:
How about adding a Conn field instead?
type ConnectionState struct { ... Conn *Conn }
Sorry, something went wrong.
How about adding a Conn field instead? type ConnectionState struct { ... Conn *Conn }
also sounds great. I can use Conn.RemoteAddr()
No branches or pull requests
Proposal Details
In certain cases it might be usefuy to have the remote address on the connection state.
For example, I want to validate during handhsake process (VerifyConnection callback) that the peer certificate was issued with the remote address.
The text was updated successfully, but these errors were encountered: