Data URI scheme: Difference between revisions

Revision as of 20:28, 5 November 2005

Revision as of 20:34, 5 November 2005

Line 10:

* Web browsers are typically limited to four concurrent connections to a server, so inline data frees up a download connection for other content.

* Browsers manage fewer cache entries for a file that contains data: URLs.

* Environments with limited or restricted access to external resources may embed content when it is disallowed or impractical to reference externally. For example, an advanced HTML editing field could accept a pasted or inserted image and convert it to a data: URL to hide the complexity of external resources from the user.

===Disadvantages===

Line 18:

* URL-encoded data: URLs can be up to three times larger (in extreme cases) than the original text content.

* Information that is embedded more than once is redownloaded as part of the containing file, and does not benefit from the browser's cache.

* Browser limits to URL length provide a maximum data size. For example, URLs in Opera are limited to around 4100 characters.

==Format==

Line 66:

'd%3E%0D%0A%3Cbody%3E%3Ch1%3E42%3C%2Fh1%3E%3C%2Fbody%3E%0D%0A%3C%2Fhtml%3E'+

'%0D%0A','_blank','height=300,width=400');

==Limitations==

While a URL should be essentially unlimited in length, some [[web browser]]s do not support this. For example, URLs in Opera are limited to around 4100 characters. Authors should restrict the use of data: URLs to small files only.

==See also==