Re: [whatwg/fetch] Define data: URLs (#579)

OK, I pushed a test for "data:x/x;base64;charset=x,WA" to https://github.com/w3c/web-platform-tests/pull/6890. w3c-test.org isn't updating (@sideshowbarker FYI) so I set up my own temp server. Conclusion is that like the ";base64;" case, it's treated as base64 by Chrome, Edge and Safari, but not by Safari. Given that a real case of this was found in the wild (barra.to.gov.br) I think it'd be best if we can keep this working.

Similarly for the other cases. It's much more likely that something depends on this working that something depends on it *not* working, so making it works minimizes the number of engines that need to work and the overall risk.

How should it work then, if not by checking for a trailing ";base64"? I see two options:
* More elaborate pre-parsing
* Letting https://mimesniff.spec.whatwg.org/#parse-a-mime-type also return whether base64 was found anywhere (but dropped because of "parameterValue is not the empty string").

I think the latter seems a bit better. @annevk?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/579#issuecomment-355287856