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
go version
$ go version
1.15.6
Yes
go env
$ go env
net/http package Server struct in the SDK have ConnState func(net.Conn, ConnState), But not exists in the 'Server' struct of 'x/net/http2'
net/http
Server
ConnState func(net.Conn, ConnState)
With the h2c feature, when the state variable is converted to http.StateHijacked , I will no longer know the subsequent state of the connection.
h2c
http.StateHijacked
I expect to be able to follow the status of this TCP connection until it is closed.
Is there such a function or a flexible solution? Thank you
The text was updated successfully, but these errors were encountered:
Hi, fsyyft
The Go project doesn't use the issue tracker for questions. See https://golang.org/wiki/Questions.
Sorry, something went wrong.
@mengzhuo is correct. We don't use the issue tracker for questions. Thank you for your interest in Go!
No branches or pull requests
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
net/http
packageServer
struct in the SDK haveConnState func(net.Conn, ConnState)
, But not exists in the 'Server' struct of 'x/net/http2'With the
h2c
feature, when the state variable is converted tohttp.StateHijacked
, I will no longer know the subsequent state of the connection.I expect to be able to follow the status of this TCP connection until it is closed.
Is there such a function or a flexible solution? Thank you
What did you see instead?
The text was updated successfully, but these errors were encountered: