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

OK, so I was testing at the wrong level, simply parsing and serializing data: URLs doesn't do it, but passing throw fetch() would?

> Chrome refuses to fetch `;charset=`. `;charset` results in the default MIME type (so also treated as an error of sorts, but different).

That seems weird.

> Firefox consistently ignores `;charset=` and  just `;charset`, returning the MIME type without that parameter.

I like that better.

Ultimately, though, I'm not at all attached to the details here, as long as we get interop with low compat risk.

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