This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
User agents start to allow fetching of data URLs in the context of XMLHttpRequest. That has implications for status/statusText/getResponseHeader()/getAllResponseHeaders(). Those implications need to be defined. Ideally in the data URL standard just like they are for blob URLs, but otherwise maybe in XMLHttpRequest for now. Henri also suggested adding a note to those four members to point out this issue to implementors.
I have done this: http://dvcs.w3.org/hg/xhr/rev/063d0f0d429d Henri, is this good enough?
(In reply to comment #1) > I have done this: > > http://dvcs.w3.org/hg/xhr/rev/063d0f0d429d > > Henri, is this good enough? I think you should handle the case where the data URI does not include the media type. Choices: a) use the defined default, or b) do not define the Content-Type header field b) is probably less surprising.
I think we should include it, otherwise for "document" it would be treated as XML.
Done: http://dvcs.w3.org/hg/xhr/rev/d9af8c30a79a
Looks OK. Thanks!
Ignore this comment please. I'm just testing out bugmail.
And ignore this comment too please. Trying again..