uNetworking / uNetworking/uWebSockets
Content-Encoding and compression support in Transfer-Encoding
Open
Nobody has claimed this yet.
Http
- Dominant language
- C++
- Stars
- 19k
- Forks
- 1.9k
- Avg merge
- 3h 24m
- Merged PRs (30d)
- 5
Description
Should automatically be handled, exposing the uncompressed data in onData handler as needed.
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 tracing the HTTP request handling path to the onData handler and identify how Transfer-Encoding and Content-Encoding are currently processed. Define the expected behavior for compressed bodies, then verify that onData receives uncompressed data without regressing existing transfer handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100