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

Having required `;base64` to be last what is left is deciding how MIME types are parsed and then serialized.

E.g., `text/HTML;` becomes `text/html` in Chrome and Firefox. Parameter names are lowercased too: `text/html;CHARSET=UTF-8` becomes `text/html;charset=UTF-8`.

I think that's a reasonable model. The only thing I'm unsure about is:

1. Preserving unknown parameters. I think this would be much better for a generic URL scheme.
2. Parameters with bugs. E.g., parameters are required to have a value. Technically per the RFC if one doesn't have a value that makes the entire MIME type not parsable, just like `text/html;` is an error, but that's not tenable. Maybe we should just drop parameters that don't have a value?

-- 
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-330542244