Talk:Data URI scheme

message: I think this article should be renamed to data: URI, and replace all references to URL with URI, retaining the historical aspect of them being called URLs. data: URL should be redirected there. Hrvoje Šimić 12:42, 17 November 2005 (UTC)
replies: text: It's a tricky issue. Let me try to explain why I think data: scheme URIs should not be considered URLs, despite they being called that in the relevant specification. They are URIs, even if you consider them URLs, since all URLs are URIs. The RFC 2397 calls them URLs, but I haven't found any formal or informal references implying that they should be considered URLs. It's as if the authors didn't know what URIs mean, so they called them URLs. RFC 3986 (see section 1.1.3) and documents from the Technical Architecture Group specify that URIs should not be considered URLs if they are not explicitly used as locators. In particular, URI schemes are not to be classified as specific URL or URN schemes. Hrvoje Šimić 09:38, 21 November 2005 (UTC)
replies: text: Well, I'm going around clearing up all the articles we have on the topic, and I think we need a standard and uncontroversial naming scheme. Since all URLs are also URIs, I figure that all "URL schemes" are also "URI schemes", so at worst it is "not specific enough" to use the latter. For consistency, therefore, I'm going to rename all the articles about schemes which deserve an article "<scheme>: URI scheme". I'm also going to put in place lots of redirects, because I actually missed this page when searching once, and almost created a new one. I hope no one is "offended" by this, it just seems sensible to be consistent. - IMSoP 22:49, 8 December 2005 (UTC)
replies: text: Sounds reasonable. -- Brianiac 22:16, 22 March 2006 (UTC)

text: After much consideration, I have to disagree about the URI designation. Not only is the standard explicit, but URI is used to refer to URLs and URNs, it isn't an actual concrete type itself. Data URLs are not URNs because they are not an identifier; they don't represent a name, nor any kind of canonical designator. It locates the data, i.e. inside the URL itself, ∴ URL. Brianary (talk) 15:19, 31 March 2015 (UTC)
thread_title:  They are really URIs 

message: Just a note on data uri's in CSS. Non-alphabetic characters must be escaped by backslashes. Refer to this bugzilla entry:https://bugzilla.mozilla.org/show_bug.cgi?id=319779
: Updated the bugzilla entry. No backslashes are necessary save for the comma, and that can be skipped if the URL is quoted. Brianary (talk) 18:46, 18 August 2008 (UTC)
replies: text:  Another update:  I've found that with quotes, you still can't have unescaped line breaks (Chrome 47 & Firefox 43 on Debian). Adam KatzΔ☎ 19:31, 28 January 2016 (UTC)
thread_title: Data: URIs in CSS

message: Also, I would like to add data: URI examples but how do I link to them? I tried [data:,] and <a href="data:,"> formats but neither are turned into links... How do I do this? (Boborok 16:05, 10 May 2006 (UTC)
replies: text: Its better to avoid them, bcoz it wont be accessible by 85% (whatever the market share of ie is) of the web browsing public. --soUmyaSch 19:30, 10 May 2006 (UTC)
replies: text: These stats  show 72% but I think it would be significantly less among users reading the data: URI article. Anyway it looks like there is no way to add them :) (Boborok 21:34, 10 May 2006 (UTC)
thread_title:  data: URI examples 

message: According to this: http://blogs.msdn.com/ie/archive/2007/12/19/internet-explorer-8-and-acid2-a-milestone.aspx#6810063  —Preceding unsigned comment added by 70.183.120.25 (talk) 08:44, 20 December 2007 (UTC)
thread_title:  Looks like IE8 should support this 

message: I removed:
: Early versions of Internet Explorer treated unrecognised about: URIs as HTML source, so something like about:bold in these versions was broadly equivalent to data:text/html,bold in browsers that support data: URIs
because
* No references
* Doesn't specify which versions
* Not even quite true: Whereas data: URIs are most useful in including an image, like data:image/gif;base64,aoeu023ithaoeu, not displaying bold text or a web page. About: would not seem to be very equivalent.
* Not a very useful fact, since it does not provide an alternative to data: as the latest versions of IE do not support it, and as it would not allow the inclusion of images (AFAIK) as notod above.
* For something so irrelevant, it was one of the first things in the article. Perhaps it should be moved to something like a "see also" section.
If you disagree, please discuss it. --Temporitron (talk) 19:45, 10 January 2008 (UTC)
thread_title:  IE about: urls 

message: : Disadvantages include greater server CPU and disk use unless a server-side cache is used.
I'm going to quibble with this. Disk use is not necessarily increased... if the script is generating a CSS page, the server only has to access the image files exactly as many times as it would have if they were referenced in the standard way: either the server loads the file to create the base64 encoding, or the client makes the server serve the file when the client is rendering the page. I removed the bold section and feel it should stay gone. --Temporitron (talk) 19:57, 10 January 2008 (UTC)
thread_title:  server-side / PHP 

message: The commentary about Safari needs some clarity. I've read the paragraph several times and can't tell if it means yes, Safari does render data: URIs, or no it doesn't. (In fact, Safari 3 does.) Using "although" starts an inversion, a negating clause. Can that paragraph be rewritten so any average reader would know what the final answer is? I can't because I'm not sure what point it was making exactly.
John Sinclair (talk) 08:34, 25 May 2008 (UTC)
thread_title:  Safari 3 

message: "Cookies are not supported." - Eh? Isn't this rather like saying that  tags don't support cookies?  —Preceding unsigned comment added by 81.2.73.194 (talk) 12:58, 20 June 2008 (UTC)
replies: text: Cookies can be part of any HTTP request, and so in the unlikely event that a web site changed what file it sent in the HTTP response based on cookies, data URIs could not be used. Really though, it's a minor problem because the host document can still use cookies. —Remember the dot (talk) 04:51, 22 August 2008 (UTC)

text: No, it's like saying that cookies aren't supported on items loaded over the FTP or Gopher protocols, given that that is the case. Nitro2k01 (talk) 17:54, 18 June 2011 (UTC)
thread_title:  Cookies 

message: Today the last paragraph of the summary says "and data URIs have now been implemented in most browsers" though I don't really understand when that was written, when is "now". Should say something like "and data URIs have been implemented in most browsers by 2009" or whenever that happened. --93.172.144.206 (talk) 15:20, 23 March 2009 (UTC)
thread_title:  Summary Paragraph 

message: I'm sure data: worked in some earlier versions of IE - around 2003 ? Or was it just in HTML emails viewed in Outlook (Express) ? Maybe it was undocumented ...
--87.194.174.252 (talk) 10:57, 5 August 2009 (UTC)
thread_title:  Internet Explorer, Outlook, Outlook Express 

message: Could somebody rewrite "features/UA detection/discrimination" without the slashes? I can't understand it. Unfree (talk) 21:26, 6 December 2009 (UTC)
thread_title: Slashes

message: Added "with base64", as the ability to add whitespace is not a general property of data URIs, but is a property of the base64 encoding. Nitro2k01 (talk) 22:24, 21 May 2011 (UTC)
thread_title:  "data URIs encoded may contain whitespace for readability." 

message: I see no mention of this URI scheme with another use that has come into play:  A VoIP "do not call" function.  Example (fictitious):
2.1.2.1.5.5.5.0.0.8.1.e164.org. IN NAPTR 100 10 "U" "E2U+X-DNC" "!.*!data:,2047!" .
See http://www.e164.org/wiki/DoNotCall for further details regarding this usage. - 71.106.211.51 (talk) 23:06, 29 December 2011 (UTC)
thread_title:  Other Uses. 

message: Surely this only applies if the same data is naively inserted several times into the source. It could just as well be a single Javascript variable, referenced as many times as needed. Unless I'm missing something, this entry should be removed from the list. 195.212.29.89 (talk) 11:23, 4 February 2014 (UTC)
thread_title:  "Referencing the same resource (such as an embedded small image) more than once from the same document results in multiple copies of the embedded resource." 

message: I removed an outdated assertion that most browsers limit the number of connections to a web server to 2.  Although this is the recommended value by the HTTP RFC, most current browsers ignore this recommendation and use a higher figure.  I've included a reference to back this claim up - although it is self-published (a blog) it is published by an acknowledged expert in the field (Steve Souders, who is currently employed as the chief performance engineer at google) who has previously been published on the subject area (High Performance Web Sites: Essential Knowledge for Front-End Engineers, O'Reilly 2007), so should meet all requirements of WP:V. 212.159.69.4 (talk) 07:26, 10 February 2014 (UTC)
thread_title:  Parallel connections 

message: The data segment is describe as being octets of letters and numbers only and required %nnn encoding otherwise. I suspect this constraint is with respect to the character set selection and seems to be irrelevant when the data is binary encoded via the base64 designation, as shown in the examples.  — Preceding unsigned comment added by 99.244.115.138 (talk) 22:40, 15 February 2016 (UTC)
replies: text: This is incorrect. See Section 3 of RFC 2397, Syntax, and Section 2 of RFC 2396, URI Characters and Escape Sequences.  — Scott • talk 23:10, 15 February 2016 (UTC)
thread_title:  The Data segment description is wrong 

message: Why is the title "data URI scheme"? Shouldn't it be "Data URI scheme"?
--Mortense (talk) 11:16, 26 January 2021 (UTC)
replies: text: I don't know why the title was changed to lowercase: was the original capitalization correct? Jarble (talk) 19:08, 16 February 2021 (UTC)
replies: text: The title of the the RFC that standardised it is 'The "data" URL scheme'. Note here that "data" is not a part of the sentence, it is the name of the scheme - it is not just "a scheme for data", it is "a scheme whose name is data"; and since case matters in computing, it is not "a scheme whose name is Data" either. The distinction is perhaps easier to understand with something like mailto which isn't an English word - "mailto" is just the string of letters that identifies that scheme, and is always lower-case, so writing "Mailto" wouldn't make sense. - IMSoP (talk) 18:25, 17 February 2021 (UTC)
thread_title:  Lowercase title