http-rs / http-rs/tide-websockets

Server does not send subprotocol.

Open
#24 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
75
Forks
21
PR merge metrics
No merged PRs in 30d

Description

Hello,

I want to implement a WebSocket connection with Sec-Websocket-Protocol present in the header. Currently, based on the examples provided by this repo, the server does not send a Sec-Websocket-Protocol back in the response header of the upgrade, even though I see in the tide Websocket Implementation the header shall be appended inside the upgrade function if Sec-Websocket-Protocol is present in the client header.

Greetings

Contributor guide

Open the contributing guide

Research direction

Start with the WebSocket upgrade implementation referenced in the issue and run the repository's examples with a client that sends Sec-WebSocket-Protocol. Compare the upgrade response headers with the requested protocol. Done means the server response includes the negotiated subprotocol when the client supplies Sec-WebSocket-Protocol.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.