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

Empty Sec-WebSocket-Protocol: in response #7

Closed
Lerc opened this issue Jun 7, 2013 · 0 comments
Closed

Empty Sec-WebSocket-Protocol: in response #7

Lerc opened this issue Jun 7, 2013 · 0 comments

Comments

@Lerc
Copy link

Lerc commented Jun 7, 2013

If the request has no Sec-WebSocket-Protocol: field the response returns with a Sec-WebSocket-Protocol: field that is present but has no value. This causes chrome to give an error of "failed: Invalid UTF-8 sequence in header value"

Interestingly, the binary versions available for download don't do this.

A workaround browser-side is just to specify a protocol

var ws = new WebSocket(uri,"dummyprotocol");

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants