ProxymanApp / ProxymanApp/Proxyman
Support for HTTP/3
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Description
At the moment, all intercepted HTTP/HTTPS through Proxyman will be downgraded to HTTP/1.1. We should support HTTP/3 too and implement the HTTP/3 parser correctly.
Why this feature/change is important?
- Determine whether or not the request is HTTP/3
- Write HTTP/3 Parser
- Work with current architecture. HTTP/1.x, HTTP/2 and HTTP/3
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 names no files, tests, or entry points. Begin by examining the current HTTP/1.x and HTTP/2 handling, then determine how HTTP/3 requests are identified and where the parser must integrate. Done means HTTP/3 is detected, parsed correctly, and works with the existing architecture.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100