client: tunneling via CONNECT method example
Open
Nobody has claimed this yet.
A-client
A-docs
E-easy
- Dominant language
- Rust
- Stars
- 16.3k
- Forks
- 1.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 14
Description
I'd like to use CONNECT method with HTTP (at least with 1.1, and, ideally with 2).
However, I don't think there's a way to unwrap the underlying stream from HTTP response.
Practically, I need an object that implements futures::io::AsyncRead and futures::io::AsyncWrite (from futures 0.3). Similar thing via tokio should work too.
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
The issue names no files or tests. Start by tracing the client-side handling of HTTP CONNECT and how the response exposes its underlying stream. Done means a CONNECT response can provide a futures AsyncRead/AsyncWrite stream, with Tokio support and HTTP/2 considered as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100