Proxy support
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go
- Domain
- networking
Research direction
Start by reviewing the proposed golang.org/x/net/proxy API and the referenced main.go around line 107. Determine how HTTP and SOCKS proxy configuration should reach the client's dialer, including support for a caller-provided dialer or creation function. Done means both proxy types and custom dialer injection are supported and covered by tests.
Written by the indexing model from the issue text.
Description
Can you add HTTP and SOCKS proxy support?
Maybe via the api from golang.org/x/net/proxy
https://github.com/jackpal/Taipei-Torrent/blob/6808fdfe24b4db505476ef48b9e288a5e7398f77/main.go#L107C6-L107C21
And it's better to make it possible to pass your own dialer creation function or dialer altogether.
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Bob Shell support Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
santhosh-tekuri/jsonschema#276 ·