feat: enable reqwest socks proxy support for provider traffic
Open
Beginner friendly
Nobody has claimed this yet.
enhancement
priority: low
question
- Dominant language
- Rust
- Stars
- 19.9k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 30
Description
Hi would it be much trouble to allow provider http traffic to route through a socks5 proxy set via HTTP_PROXY/ALL_PROXY=socks5h://....
For http the change may be as simple as:
--- a/crates/jcode-provider-core/Cargo.toml
+++ b/crates/jcode-provider-core/Cargo.toml
-reqwest = { version = "0.12", default-features = false, features = ["json", "stream", "charset", "http2", "system-proxy", "rustls-tls", "rustls-tls-native-roots"] }
+reqwest = { version = "0.12", default-features = false, features = ["json", "stream", "charset", "http2", "system-proxy", "socks", "rustls-tls", "rustls-tls-native-roots"] }
probably doesn't cover websockets but that may be a second step.
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 in crates/jcode-provider-core/Cargo.toml and inspect the reqwest dependency and provider HTTP traffic setup. Verify how HTTP_PROXY and ALL_PROXY are handled, then confirm provider HTTP requests can use a socks5h proxy; websocket support is explicitly outside this issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100