websockets-rs / websockets-rs/rust-websocket
Only tries to connect to the first DNS result and doesn't try following results
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
See https://github.com/centricular/gstwebrtc-demos/issues/120
Pretty standard usage of ws connecting to wss://webrtc.nirbheek.in:8443 via async_connect().
What happens here is that it resolves to 2a01:7e00::f03c:91ff:feae:244 and 176.58.110.251, tries the first, gets connection refused and does not even try the next one.
Contributor guide
No contributing guide indexed for this repository
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 at sendrecv/gst-rust/src/main.rs around the async_connect() call at lines 799-802, then trace how the wss://webrtc.nirbheek.in:8443 address is resolved and attempted. Check the connection path for handling multiple DNS results; done means a refused first result does not prevent trying the next available address.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100