Connection timeout with wss: URLs
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.3k
- Forks
- 1.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 14
Description
Version
0.14
Platform
Linux 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Description
When attempting to perform a Websocket handshake given a URL with wss: scheme, the connection times out (as if the target port wasn't 443). I've checked that port 443 is open, and it works with the https: scheme.
For a short example that shows this behavior, please see this repo. (The particular url used in this example belongs to office.com.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked hyper_wss_issue reproduction and compare the wss: handshake with the working https: case on the reported office.com URL. Trace how the wss: scheme selects its connection port and confirm the fix by reproducing a successful connection to port 443 without a timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100