Websocket returns error through tunnel about tunnelto

[agrinman]

So yes it turns out this is something tunnelto needs to handle as it was previously not processing the WebSocket upgrade. #42 add supports for this and will be merged shortly...

[agrinman]

Fixed it 0.1.16!

[agrinman]

Thanks for the bug report, will look into this

[hirschenberger]

Same issue here. Very sad.

[gzimh]

I don't think this is realted to tunnelto. Inavlid frame header is usually a result of SSL mismatch.
The client request should be secured (e.g socket.io):

const socket = io.connect('https://<subdomian>.tunnelto.dev', {secure: true});

or, just use the http version of the generated tunnel:

const socket = io.connect('http://<subdomian>.tunnelto.dev');