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
x/net/websocket: Missing EOF in TLS encrypted websocket connections #2147
Labels
Milestone
Comments
Comment 1 by nroos@webware-experts.de: Tried that on several Linux systems; finally installed a fresh, current Debian in a VM and used a current Go version (downloaded with "hg clone -u release https://go.googlecode.com/hg/ go"). The reported problem always occurs. If anybody wants to have this VM, please contact me. Unfortunately, it's 500MB large. |
Comment 3 by nroos@webware-experts.de: With the new websocket package, the behaviour has become better and worse: Encrypted websocket connections now deliver an EOF. That's fine. Unencrypted connections now deliver a "read tcp 127.0.0.1:12345: connection reset by peer" instead of EOF. In this way, the topic "missing EOF" is still valid... |
Comment 4 by nroos@webware-experts.de: I think this issue can be switched to "fixed", it was solved with the rewritten code. With an almost current version, also the behaviour in my last comment does not seem to happen any more. Norbert |
mikioh
changed the title
Missing EOF in TLS encrypted websocket connections
websocket: Missing EOF in TLS encrypted websocket connections
Jan 14, 2015
mikioh
changed the title
websocket: Missing EOF in TLS encrypted websocket connections
x/net/websocket: Missing EOF in TLS encrypted websocket connections
Jul 30, 2015
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
by nroos@webware-experts.de:
The text was updated successfully, but these errors were encountered: