CONNECT and tunnel support
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 890
- Forks
- 136
- Avg merge
- 14d 20h
- Merged PRs (30d)
- 2
Description
From the proposal:
HTTP CONNECT to tunnel over a single QUIC stream
Curious what the status is? If nobody is working on this I'd be happy to contribute although I might need a bit of guidance.
Guidance mostly around the expected API surface. Currently inspecting h2 as a reference.
If the proxy
detects that the client has reset the stream or aborted reading from
the stream, it MUST close the TCP connection.
The client TCP connection and probably server TCP connection would be managed by the application/proxy that depends on h3 (at least for the usecases I have in mind). Is there desire to handle that forwarding in h3? I assume not.
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 by reading the proposal excerpt in this issue and inspecting h2, which it names as a reference; no h3 file or test is identified. Clarify the expected API surface and whether TCP forwarding belongs in h3, then define completion around an agreed CONNECT/tunnel design and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100