Re: Intent to ship: accept spaces and tabs in unquoted values (of e.g. "filename") used in Content-Disposition parameterized header pairs to to align with other browsers

Ugh. This does seem like the right thing to do in a bad situation. Thanks and thanks to Anne for working to get the spec updated. -Ekr On Wed, Aug 19, 2020 at 10:10 AM Gijs Kruitbosch wrote: > It's been pointed out to me that I neglected to merge the "intent to > prototype" requirements into

Re: Intent to ship: accept spaces and tabs in unquoted values (of e.g. "filename") used in Content-Disposition parameterized header pairs to to align with other browsers

It's been pointed out to me that I neglected to merge the "intent to prototype" requirements into my email. So: Platform coverage: everywhere. Preference: no pref. DevTools bug: covered by existing network tooling (it already shows the full header). Other browsers: as noted, they already do

Intent to ship: accept spaces and tabs in unquoted values (of e.g. "filename") used in Content-Disposition parameterized header pairs to to align with other browsers

As of Firefox 81 I intend to update our parsing of Content-Disposition headers so that spaces/tabs in unquoted values are treated as part of the value (rather than as a separator, cutting off the value). This is what Blink and Webkit already do. Bug for this change: