WebAssembly / WebAssembly/WASI
Header Validations
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
Some questions with regards to header validations:
- Valid headers keys must not include whitespace
- Valid header values must have whitespace trimmed
Possible clarifications that therefore might be made:
Keys
- Could clarify that they are always valid according to eg https://searchfox.org/mozilla-central/rev/9f76a47f4aa935b49754c5608a1c8e72ee358c46/netwerk/protocol/http/nsHttp.cpp#172-215 (which includes disallowing whitespace)
Values
- Could clarify that they are always trimmed by
\t,\r\and\n - Could clarify that they contain no inner
\0,\ror\n.
Without the above assumptions, returning values to the user risks returning invalid values from a get() or entries() call, making any fetch-based Headers implementation on top of these primitives non-standard.
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 by reviewing the header-key and header-value questions in the issue, including the linked Mozilla nsHttp.cpp reference and the stated get(), entries(), and fetch-based Headers implications. Resolve which validation and trimming rules should be specified; done means the expected behavior is unambiguous.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100