Yes, this is exactly the same problem we stumbled over when trying different WebSocket proxy solutions, they all had one or the other problem, or needed special handling for those subprotocol types.
Am Freitag, 20. Januar 2017 13:19:42 UTC+1 schrieb Thomas Arnbjerg: > > Problem solved. > The emscripten generated javascript sends the request header > 'Sec-WebSocket-Protocol:"binary"'. When using libwebsockets the protocol > definition with the name "binary" has to be created. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
