20045 2012-11-22 16:00:14 +0000 data: URLs, HTTP, and parsing 2013-04-12 12:43:40 +0000 1 1 1 Unclassified WHATWG Fetch unspecified PC Windows 3.1 RESOLVED FIXED P2 normal Unsorted 1 annevk annevk julian.reschke mike public-webapps sideshowbarker+fetchspec oldest_to_newest 78654 0 annevk 2012-11-22 16:00:14 +0000 data: URLs almost always successfully parse per the URL parser, but the URL processing step can go wrong. Maybe if that goes wrong it should be a 400 Bad Request? Or maybe 500 Internal Server Error? So e.g. data:test parses fine as a URL, but does not parse fine as a data: URL. 78655 1 annevk 2012-11-22 16:00:44 +0000 This question relates to http://xhr.spec.whatwg.org/#data:-urls-and-http by the way. 78675 2 julian.reschke 2012-11-23 06:59:57 +0000 (In reply to comment #0) > data: URLs almost always successfully parse per the URL parser, but the URL > processing step can go wrong. Maybe if that goes wrong it should be a 400 > Bad Request? Or maybe 500 Internal Server Error? > > So e.g. > > data:test > > parses fine as a URL, but does not parse fine as a data: URL. Sounds right to me. However, I would just require 4xx (and state that 400 is fine), in case we ever define a more specific status code. 86033 3 annevk 2013-04-12 12:43:40 +0000 This is fixed, also in XHR for now. Failure to parse will generate a network error.