Chisel Client with HTTP Proxy error
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I have an issue running chisel client on a windows 10 x64 computer using an HTTP proxy.
Command:
chisel.exe client --proxy http://<proxy_ip>:<port> <remote_host>:<port> R:socks
Output:
Connection error: unexpected EOF (Attempt: 1)
Does chisel works with only specific configuration of HTTP proxy or should it work with any HTTP proxy ?
Thx
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 with the chisel client path handling the --proxy option and reproduce the Windows command shown in the issue. Investigate the unexpected EOF response when connecting through the HTTP proxy; done means the supported proxy behavior is established and the command either works or the limitation is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100