- From: Jonas Sicking <jonas@sicking.cc>
- Date: Thu, 19 Sep 2013 16:26:55 -0700
- To: "piranna@gmail.com" <piranna@gmail.com>
- Cc: Hallvord Steen <hsteen@mozilla.com>, public-webapps <public-webapps@w3.org>
That's true for <img src="data:..."> too. Technically that's also not needed. Same with <img src="blob:..."> I think there's a lot of value in ensuring that all URL schemes work in all APIs that handle URLs. Otherwise the concept of a URL sort of falls apart. / Jonas On Thu, Sep 19, 2013 at 2:46 PM, piranna@gmail.com <piranna@gmail.com> wrote: > Are you saying it's possible to use 'data:' requests with XHR? What's > the sense for this? The data is already on the client... > > 2013/9/19 Hallvord Steen <hsteen@mozilla.com>: >> Hi, >> I see Gecko "fakes" a Content-Length header (visible to getAllResponseHeaders()) when you load a data: URL with XHR. This is wrong per the spec (which is explicitly requiring only a single Content-Type response header) but it looks more like a feature than a bug.. Should we spec it? >> >> Test: http://w3c-test.org/web-platform-tests/master/XMLHttpRequest/data-uri-basic.htm (subtest getAllResponseHeaders()) >> Current spec text: http://dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html#data:-urls-and-http >> -Hallvord R >> > > > > -- > "Si quieres viajar alrededor del mundo y ser invitado a hablar en un > monton de sitios diferentes, simplemente escribe un sistema operativo > Unix." > – Linus Tordvals, creador del sistema operativo Linux >
Received on Thursday, 19 September 2013 23:27:52 UTC