websockets

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/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.

It's so frustrating how the chromium team is ending up as a gatekeeper of the Internet by pick and choosing what gets developed or not. I recently come across another issue pertaining to the chromium team not budging on their decisions, despite pressure from the community and an RFC backing it up - in my case custom headers in WebSocket handshakes, that are supported by other Javascript runtimes like node and bun, but the chromium maintainer just disagrees with it - https://github.com/whatwg/websockets/issues/16#issuecomment-...

The anchor got stripped. The comment is here: https://github.com/whatwg/websockets/issues/16#issuecomment-... The commit on Github is here: https://github.com/kubernetes/kubernetes/commit/714f97d7baf4...

Really appreciating bun's ability to set custom WebSocket headers. Incidentally, what's up with the resistance against this from the standards maintainers? [1] The request exists since 2017, there are tons of use cases and developer interest, but Chrome refuses implementation on technicalities. What gives? [1] https://github.com/whatwg/websockets/issues/16