https://github.com/whatwg/websockets/issues/16 https://github.com/whatwg/websockets/issues/16 No, I don't think you get it. `new Websocket()` from JS takes no

https://github.com/whatwg/websockets/issues/16 https://github.com/whatwg/websockets/issues/16 No, I don't think you get it. `new Websocket()` from JS takes no arguments for headers. You literally can't send headers during the handshake from JS. https://developer.mozilla.org/en-US/docs/Web/API/WebSocket/WebSocket https://developer.mozilla.org/en-US/docs/Web/API/WebSocket/W... Actually will look into using the subprotocol as a way to do auth, but most impls in the wild send the auth as the first message. The fact the protocol in theory supports it doesn't really matter much since no browser implements that part of the spec.