Can chisel not use websocket or HTTP CONNECT?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
I tried to capture the packet and confirmed that chisel uses websocket to transmit TCP traffic., like this:
If the firewall only allows HTTP traffic and websocket is not allowed, chisel will not work.
Can chisel only use HTTP?
I find a similar thing called Bidirectional-streams Over Synchronous HTTP (BOSH).
https://en.wikipedia.org/wiki/BOSH_(protocol)
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
The issue does not name any files, tests, or entry points. Start by tracing chisel’s current WebSocket transport and compare it with the requested HTTP-only or BOSH-style approach. Done requires a decided protocol design and a working transport that functions when WebSocket and HTTP CONNECT are unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100