WebAssembly / WebAssembly/WASI
p3(http): Consider specifying the list of definitely forbidden field names
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
Field operations such as from_list or set may return a header-error. It is currently not specified which field names might cause these operations to return header-error.forbidden.
Wasmtime's implementation defines a list of default forbidden headers, which according to https://github.com/bytecodealliance/wasmtime/pull/7538#issuecomment-2313640999 that list is an evolution from what I believe is an original design document of the WASI HTTP spec.
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
Start with proposals/http/wit/types.wit at from_list and set, then compare Wasmtime's default forbidden headers in crates/wasi-http/src/lib.rs with the linked design document and cited discussion. Done means the WASI HTTP specification clearly states whether and which field names are forbidden.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- backend-api-design, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100