Server boilerplate
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 361
- Forks
- 165
- Avg merge
- 17h 34m
- Merged PRs (30d)
- 5
Description
Is there a reason beyond "nobody's done it yet" that TlsAcceptor and TlsStream from the server example aren't published by this library? As it is hyper-rustls doesn't directly connect hyper and rustls.
Also it looks like the HTTP2 ALPN negotiation is on by default for the client per https://github.com/rustls/hyper-rustls/pull/95 but not the server (by the example) -- is there a reason for this?
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 server example's TlsAcceptor and TlsStream and comparing its ALPN setup with the client behavior described in hyper-rustls PR 95. Determine whether publishing the server types and enabling HTTP/2 ALPN are intended API changes; done means the maintainers have a decided scope for the library and example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100