Mark Nottingham
Mark Nottingham
Discussed offline with @reschke. Absent more information, we think the best path forward is to add a security consideration along the lines of: > Caches that normalize QUERY content incorrectly...
Discussed offline with @reschke. This seems orthogonal to QUERY - it's also useful for eg POST. See also https://httpwg.org/specs/rfc7240.html#return
It's either a SF or not - you can't both define it as a SF and also re-use existing parsers. If we go SF, it would either be a List...
Yes, as long as it's the right one.
I think this issue can be closed now.
Relevant part of the spec is [5 Fetching](https://fetch.spec.whatwg.org/#fetching). See also [this mozilla bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1249474), which moved them to `*/*` for images. It gives some rationale for how to manage these values.
FWIW - `*/*` is always implied; they only reason you'd want to include it explicitly is if you want to say `*/*;q=0` -- i.e., "don't send me anything else."
As these are unadopted drafts, it's likely too early to register, but I'll leave the issue open here to 'soft' reserve them. For the name, have you considered registering one...
As these are unadopted drafts, it's likely too early to register, but I'll leave the issue open here to 'soft' reserve them. For the name, have you considered registering one...
This is a third-party registration of a value that's mentioned briefly in a _very_ old W3C Interest Group note - any thoughts @plehegar? I also note that the reference doesn't...