Repository navigation
Forbid non-ascii field names #786
Description
Right now, the field-name production is a string which is specified to be compared case-insensitively with regards to equality. Case-insensitive comparisons are cheap to do for ASCII, but a bit annoying for full unicode. Fortunately (?), field names are always ASCII; values are not but that's OK. So, what about adding a restriction in wasi:http that forbids non-ascii field names?
Activity
wingo commentedon Sep 2, 2025
Alternately, one could specify field names as
list<u8>, and use the byte-lowercase algorithm fromfetch: https://infra.spec.whatwg.org/#byte-lowercaselukewagner commentedon Sep 2, 2025
If we restrict field-name to RFC 9110's
field-nameas discussed in #791, then I believe we end up with a subset of 7-bit ASCII?