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
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");
The text was updated successfully, but these errors were encountered:
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");
The text was updated successfully, but these errors were encountered: