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?
Currently go.net/websocket provides no way to send cookies back over the initial WebSocket HTTP "Upgrade" request (the first request made).
In my current application, because of this we must send another single useless HTTP request in order to get cookies back from the Go server.
There was an discussion about this exact issue on the ML back in 2011 (see https://groups.google.com/forum/?fromgroups=#!topic/golang-nuts/5dxVevxkMa0)
What is the expected output?
go.net/websocket should provide an way to read and respond to cookies (and possibly
other headers?) in an close manner to the way net/http allows you to.
The text was updated successfully, but these errors were encountered:
mikioh
changed the title
go.net/websocket: allow for reading and sending cookies, other HTTP headers
websocket: allow for reading and sending cookies, other HTTP headers
Jan 4, 2015
mikioh
changed the title
websocket: allow for reading and sending cookies, other HTTP headers
x/net/websocket: allow for reading and sending cookies, other HTTP headers
Jul 30, 2015
The text was updated successfully, but these errors were encountered: