You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
WASIp3 request#set-scheme is more lenient than RFC 9110 #11778
RFC 3986 §3.1, referred to by RFC 9110, specifies that URI schemes should begin with an ascii alphabetic character and then continue the same but also allowing +, -, numbers and .:
And in Wasmtime, we have the expected behavior in that request.set_method allows the productions above and rejects most others, but it is more lenient in that it allows schemes that begin with a character in +-.0123456789~. Probably that needs tightening up.
We should probably also eagerly lower-case "other" schemes, i.e. that get-method after set-method("A") should return "a":
Although schemes are case-insensitive, the canonical form is lowercase and documents that specify schemes must do so with lowercase letters. An implementation should accept uppercase letters as equivalent to lowercase in scheme names e.g., allow "HTTP" as well as "http") for the sake of robustness but should only produce lowercase scheme names for consistency.
Activity
wingo commentedon Oct 2, 2025
We should probably also eagerly lower-case "other" schemes, i.e. that
get-methodafterset-method("A")should return"a":