GET Request on proxy, <WARNING> non-binary msg
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Hi there !
We're using Chisel behind a proxy and it's work very well !
Sometime I've this request (GET) on our proxy. Here are the request headers :
HTTP Chisel GET
host = xx.xxx.xx.xx:80
user-agent = Go-http-client/1.1
sec-websocket-key = MeS4t77DbFRSyf3bcisOdQ==
sec-websocket-protocol = chisel-v2
sec-websocket-version = 13
via = HTTP/1.1 forward.http.proxy:3128
connection = keep-alive
What should I do with this request? Is this normal? Usually we only get upgrades.
Sometime on stderr of chisel we've:
<WARNING> non-binary msg
<WARNING> non-binary msg
<WARNING> non-binary msg
Is this normal ?
Is there a link between these two message / request ?
Thanks for your support !
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
No files or tests are named. Start by reproducing the proxy GET request and the “non-binary msg” warnings, then trace the proxy and WebSocket handling paths to determine whether they are related. Done means documenting the expected behavior and identifying a focused fix or confirmed normal operation with regression coverage if appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100