websockets-rs / websockets-rs/rust-websocket
Using ClientBuilder For HTTP Authentication
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
As websocket does not specify an authentication mechanism, I'm probably going to use standard http(s) authentication (e.g., username/password) or token. Is it possible to do this through the ClientBuilder API or do I have to use a separate method such as HttpClientCodec?
I want to re-use the TLS stream and possibly any cookies or headers set by the server.
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 by reviewing the ClientBuilder API and HttpClientCodec references in the issue, focusing on how the TLS stream, cookies, and headers could be reused. Determine whether HTTP authentication can be supported through ClientBuilder or requires a separate method, and clarify the expected API behavior before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- authentication, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100