HEAD requests cause "unexpected end of file" from gzip decoder
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 336
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
It appears HEAD requests cause the gzip decoder to throw an 'unexpected end of file' error. This is likely because the HEAD has a Content-Length but no body frame.
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 a HEAD request against the fetch-h2 client and trace how its response reaches the gzip decoder. Confirm the request completes without an unexpected end-of-file error while preserving normal handling for responses with bodies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100