uNetworking / uNetworking/uWebSockets
Chunked encoding parser fixes
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 19k
- Forks
- 1.9k
- Avg merge
- 3h 24m
- Merged PRs (30d)
- 5
Description
We currently score 147/159 in Http11Probe and at least 5 of remaining failures are only due to Chunked extension parsing. These would all be fixed with a stricter parser. At that point, we would be more compliant than 85% of servers
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 locating the chunked extension parser and the Http11Probe results referenced in the issue. Review the remaining probe failures to determine the required parsing behavior and use them as the acceptance check. Done means the stricter parser resolves the identified chunked-extension failures without regressing existing HTTP parsing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100