You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Run a server with the websocket package.
2. Connect to the server and issue an incorrect or incomplete client handshake.
What is the expected output?
Client should see a 4xx HTTP status response.
What do you see instead?
Client sees connection hangup.
Which compiler are you using (5g, 6g, 8g, gccgo)?
6g
Which operating system are you using?
osx
Which revision are you using? (hg identify)
6d7136d74b65+ weekly/weekly.2011-10-18
Please provide any additional information below.
The code appears to be originating and passing around http statuses, but they are not
getting out onto the response.
The text was updated successfully, but these errors were encountered:
Thanks for the report.
I missed recent websocket spec had changed that the server needs to return an http
response with an appropriate error code.
I'll fix it soon.
mikioh
changed the title
On failed handshake, websocket server closes connection without issuing response.
x/net/websocket: On failed handshake, websocket server closes connection without issuing response.
Jul 30, 2015
by marksadamj:
The text was updated successfully, but these errors were encountered: