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

@foolip you say there are 429 data URLs with a space in them in HTTPArchive.  How many data URLs are there?  I think that is an incredibly low percentage, if Chrome and Firefox started not allowing a space they would be fixed, and that would be the right thing to do.  I do not think we should allow whitespace, and valenting's referenced comments reference a 6 year old bug that does not have a space in the data URL.

I don't feel as strongly about allowing semicolons instead of colons or allowing base64 in different locations before the actual encoded data.  I'd like to be stricter, but it wouldn't bother me too much if we all became more permissive together in a well-defined manner.

Is there significant non-browser use of data URLs?  They would probably respect the RFC over the fetch spec.

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