Skip to content

Specify the RFC 9110 field-name syntax in wasi-http - #967

Closed
sainimal1ba-hue wants to merge 1 commit into
WebAssembly:mainfrom
sainimal1ba-hue:http-field-name-rfc9110
Closed

sainimal1ba-hue wants to merge 1 commit into
WebAssembly:mainfrom
sainimal1ba-hue:http-field-name-rfc9110

Conversation

@sainimal1ba-hue

Copy link
Copy Markdown

Resolves #786.

The field-name docs said field names are strings compared case-insensitively, but never said what syntax a field name has. This adds a paragraph pointing at RFC 9110 as the ground truth for what should be accepted as a field name: the field-name = token production (section 5.1), which allows only ASCII characters.

service.md and middleware.md are regenerated with wit-bindgen markdown --html-in-md --all-features (wit-bindgen 0.48.1, the version the release workflow pins).

Validation: WIT_FILES=["proposals/http/wit/types.wit"] node .github/scripts/validate-proposals.js passes: wit-deps lock check, WIT parse, wasm encoding, Component Model feature validation, @SInCE annotations.

The field-name docs left it unstated what syntax a field name follows.
State that RFC 9110 defines it and allows only ASCII characters, and
refer to it as the ground truth for what should be accepted as a field
name, as asked for in the wasi-http champions triage of WebAssembly#786.
@sainimal1ba-hue
sainimal1ba-hue requested a review from a team as a code owner November 14, 2026 12:39
@github-actions github-actions Bot added the P-http Proposal: wasi-http label Nov 14, 2026
@pchickey

Copy link
Copy Markdown
Contributor

I'm not inclined to review contributions from a first-time contributor to WebAssembly who doesn't have any other history related to Wasm in their profile. This is work I expect to be done by a human, not by an LLM.

@pchickey pchickey closed this Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

P-http Proposal: wasi-http

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Forbid non-ascii field names

2 participants