Luke Oliff
Luke Oliff
> Is it possible to fix this on the server? See [websockets/ws#2244 (comment)](https://github.com/websockets/ws/pull/2244#issuecomment-2245214238) I believe this refers to your server, when you're running the SDK code. I am not sure...
> It's exactly where you pointed. `NATIVE_WEBSOCKET_AVAILABLE` is true if `WebSocket` is defined. Since I assign `global.WebSocket = WebSocket` then in my case it is defined. > > I use...
> While I see your point, he is right that servers should conform to the RFC and not make assumptions about the input. The performance overhead is negligible for this...
> I have to say that actually _stripping out_ the space should have performance impact more than handling a header without a space. Did you check the server logic? Ok
We'll pin v7 until we have a moment to discuss a change to our auth service. Thanks for your help
@orgads we now have a PR in review to resolve this on our service. I will let you know once it has been released
This has now been released on our API
Did you manage to spot any errors in a node or browser console? It should support at least Node 20