WebSocket connections that negotiate a subprotocol are not completing the upgrade correctly because the…
WebSocket connections that negotiate a subprotocol are not completing the upgrade correctly because the…: a task in LegoFlow-SWE (Harbor dataset). and the server accepts that protocol through a call to websock accept proto(...) , the upgrade response must also include the same…
The task
and the server accepts that protocol through a call to `websock_accept_proto(...)`, the upgrade response must also include the same `Sec-WebSocket-Protocol` value. Right now the request can be accepted, but the response omits the header, so the handshake is incomplete from the client’s perspective.
Part of Lego-X/LegoFlow-SWE.