Request protocol for WebSocket upgrade request is always http about opine HOT 2 CLOSED

Actually, I don't believe this is what we want - the ws handshake is performed over HTTP so what you're seeing in Opine is that initial handshake request and the protocol is as expected.

Once the connection is established and the connection upgrade executed then the ws protocol is used, but by this point we're no longer in the remit of Opine's request middleware, instead performing event handling on the connections themselves.

It would be incorrect to indicate that the initial handshake is using a ws protocol when it isn't.

The opening handshake is intended to be compatible with HTTP-based server-side software and intermediaries, so that a single port can be used by both HTTP clients talking to that server and WebSocket clients talking to that server. To this end, the WebSocket client's handshake is an HTTP Upgrade request

See https://www.rfc-editor.org/rfc/rfc6455.

from opine.

Sorry taken a while to check notifications, this seems reasonable 🙂

from opine.