This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 15509 - Define HTTP handling of data URLs (and maybe other URLs)
Summary: Define HTTP handling of data URLs (and maybe other URLs)
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: XHR (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
Depends on:
Reported: 2012-01-10 20:41 UTC by Anne
Modified: 2012-02-20 15:19 UTC (History)
4 users (show)

See Also:


Description Anne 2012-01-10 20:41:07 UTC
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.
Comment 1 Anne 2012-02-16 14:24:19 UTC
I have done this:

Henri, is this good enough?
Comment 2 Julian Reschke 2012-02-16 14:37:10 UTC
(In reply to comment #1)
> I have done this:
> Henri, is this good enough?

I think you should handle the case where the data URI does not include the media type.


a) use the defined default, or

b) do not define the Content-Type header field

b) is probably less surprising.
Comment 3 Anne 2012-02-16 14:43:58 UTC
I think we should include it, otherwise for "document" it would be treated as XML.
Comment 4 Anne 2012-02-17 22:40:21 UTC
Comment 5 Henri Sivonen 2012-02-20 08:10:04 UTC
Looks OK. Thanks!
Comment 6 Michael[tm] Smith 2012-02-20 15:16:32 UTC
Ignore this comment please. I'm just testing out bugmail.
Comment 7 Michael[tm] Smith 2012-02-20 15:19:36 UTC
And ignore this comment too please. Trying again..