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

Reply via email to