Skip to content
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: server rejects requests without an origin header #4198

Closed
gopherbot opened this issue Oct 5, 2012 · 2 comments
Closed

x/net/websocket: server rejects requests without an origin header #4198

gopherbot opened this issue Oct 5, 2012 · 2 comments
Milestone

Comments

@gopherbot
Copy link

@gopherbot gopherbot commented Oct 5, 2012

by deanm@chromium.org:

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.
@rsc
Copy link
Contributor

@rsc rsc commented Oct 6, 2012

Comment 1:

Labels changed: added priority-later, removed priority-triage.

Status changed to Accepted.

@ukai
Copy link
Contributor

@ukai ukai commented May 12, 2013

Comment 2:

This issue was closed by revision golang/net@0005f0a.

Status changed to Fixed.

@mikioh mikioh added repo-net and removed repo-net labels Dec 23, 2014
@mikioh 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 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
@mikioh mikioh modified the milestone: Unreleased Jul 30, 2015
@golang golang locked and limited conversation to collaborators Aug 5, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.