ProxymanApp / ProxymanApp/Proxyman
NIOHTTP1.HTTPParserError error 22
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Description
The current request uses gRPC+Protobuf for transferring binary data, with the URL using a non-standard port 8099; for example: https://xxxx.com:8099/.
If the URL is configured as "xxxx.com:8099" in the SSL proxy list, the request will show that the SSL proxy is enabled to view the content.
If the URL is configured as "xxxx.com" in the SSL proxy list, the packet capture will convert the protocol to http, and an internal error will be displayed, returning "The operation couldn't be completed. (NIOHTTP1.HTTPParserError error 22.) (code=22)".
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 by reproducing the reported gRPC/Protobuf request on port 8099 with the SSL proxy list configured as either "xxxx.com:8099" or "xxxx.com". Compare the captured protocol and resulting NIOHTTP1.HTTPParserError error 22; done means the request is handled without the reported internal parser error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100