it uses "*" / #vary but "vary" is a token, and token allows "*" anyway. Also, see #7.
Activity
reschke commentedon Jan 9, 2020
In particular, "*" is a valid field name. We probably should reserve it in the registry.
annevk commentedon Jan 9, 2020
(CORS has an issue like that as well, including for a
*method; see the note at https://fetch.spec.whatwg.org/#http-new-header-syntax.)reschke commentedon Jan 10, 2020
Proposal:
Then state that if "*" appears, no "real" field-name is allowed to appear as well (for backwards compat).
Do we need to discuss cases like
?
royfielding commentedon Feb 3, 2020
I don't see why that is an improvement.
mnot commentedon Feb 3, 2020
I thought we were going to reserve
*and define its meaning in prose...mnot commentedon Feb 4, 2020
I.e., it should just be
reschke commentedon Feb 4, 2020
which implies registering "*" as reserved field name, right?
mnot commentedon Feb 4, 2020
Yes. That's #274
mnot commentedon Jul 2, 2020
Discussed; will create a PR to move ABNF and prose to list-based.
Make Vary always list-based
reschke commentedon Jul 13, 2020
Do we need to list that as change from 7230?
mnot commentedon Jul 14, 2020
Probably a good idea; will commit to master and link here.
Document change for #272.