Repository navigation
need to reserve field name and method name "*" #274
Description
A field name of "*" would clash with the definition of "Vary" (see #272).
A method name of "*" would clash with Access-Control-Request-Method (see https://fetch.spec.whatwg.org/#http-new-header-syntax) (ack @annevk)
Activity
[-]need to reserved field name and method name "*"[/-][+]need to reserve field name and method name "*"[/+]reschke commentedon Jan 10, 2020
...or disallow registration.
reschke commentedon Feb 2, 2020
partly blocked by #273
reschke commentedon Jun 5, 2020
To "reserve" in the method registry, we'll need to add a "comments" column to the registry. Makes sense?
cc: @mnot
annevk commentedon Jun 5, 2020
Would you leave Safe and Idempotent empty as well? Forbidding registration might be simpler?
reschke commentedon Jun 5, 2020
Good question. Maybe "n/a"?
In any case, extending the registration procedure to disallow "*" works for me as well.
mnot commentedon Jun 9, 2020
Disallowing registration is fine for me too. Should we also disallow registering it as a field name?
There are a few other ways we could do this that might be worth considering; e.g., we could require registered values to have at least two characters, or require registered values to begin with ALPHA. We already say:
reschke commentedon Jun 9, 2020
Yes, for consistency.
mnot commentedon Jul 2, 2020
Discussed; put into the registry with a comment about why it's reserved; not safe or idempotent.
reserver "*" as field name (#274)
reschke commentedon Jul 10, 2020
Note whatwg/fetch#1052
reserve "*" as method name (#274)
Merge pull request #403 from httpwg/reschke-274