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
go version go1.0.2
The websocket server rejects requests (with a 400 status code) that do not include an
origin header. Browsers send an origin header, but for non-browsers there are some
notes about this in the spec (rfc6455):
"""
This header field is sent by browser clients; for non-browser
clients, this header field may be sent if it makes sense in the
context of those clients.
"""
By default most non-browser websocket client APIs do not send an origin header, and it
would seem it's a better approach if the websocket server does not require one.
The text was updated successfully, but these errors were encountered:
mikioh
changed the title
go.net/websocket: server rejects requests without an origin header
websocket: server rejects requests without an origin header
Jan 4, 2015
mikioh
changed the title
websocket: server rejects requests without an origin header
x/net/websocket: server rejects requests without an origin header
Jul 30, 2015
by deanm@chromium.org:
The text was updated successfully, but these errors were encountered: