Forwarding the `rustls` provider settings
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 361
- Forks
- 165
- Avg merge
- 17h 34m
- Merged PRs (30d)
- 5
Description
It would be good to use a design of the features similar to axum-server, i.e.:
tls-rustls = ["tls-rustls-no-provider", "rustls/aws-lc-rs"]
tls-rustls-no-provider = [...]
This would make it easier to forward these options down the chain of dependencies.
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 inspecting the repository's Cargo.toml feature definitions and compare them with the linked axum-server Cargo.toml example. Trace how the rustls provider feature is forwarded through dependencies. Done means the feature layout supports both the default provider selection and the no-provider variant described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100