kornelski / kornelski/http-cache-semantics
Optionally remove content-encoding headers
Open
- Dominant language
- JavaScript
- Stars
- 260
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
HTTP libraries unzip the content, so the body in JS isn't strictly the same as body HTTP RFC is talking about.
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is named. Start by reading the library's response-header handling and existing tests, then clarify how callers should opt into removing content-encoding headers after decompression. Done should include a defined API behavior and tests covering the optional removal without changing the default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100