WebAssembly / WebAssembly/WASI
Clarification regarding host behaviour with `Content-Length` header
Open
Nobody has claimed this yet.
P-http
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
What is the expected/acceptable behavior in the host in terms of automatically setting the Content-Length header on behalf of the guest when the size of the body is known?
Contributor guide
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. Start by reviewing the host and guest HTTP behavior around a known body size and the Content-Length header; done means reaching and documenting an agreed expected behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100