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 5883 - data: URLs
Summary: data: URLs
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P5 minor
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NoReply
Depends on:
Reported: 2008-07-21 15:38 UTC by Justin James
Modified: 2010-10-04 14:29 UTC (History)
5 users (show)

See Also:


Description Justin James 2008-07-21 15:38:32 UTC
Currently, the RFC for data: URLs (RFC 2397 at ) omits the maximum length for a data: URL. For developers to be able to safely use data: URLs, developers need to be gauranteed a "minimum maximum" length of data: URLs. Since RFC 2397 does not specify this minimum maximum length, and since many user agents already implement multi-megabyte data: URLs, the HTML spec should set a "minimum maximum" length of data: URLs. For example:

"A user agent must accept data: URLs of at least XYZ megabytes in length."
Comment 1 Ian 'Hixie' Hickson 2008-07-21 16:27:49 UTC
In general HTML5 doesn't set any minimums, and indeed explicitly allows browsers to have arbitrary minimums. There's no guarantee that a browser will support a multimegabyte file of any kind, let alone a multimegabyte data: URI. Indeed the host machine might only have a few hundred kilobytes.
Comment 2 crisp 2008-07-21 20:48:30 UTC
IE8 currently only supports data: URLs up to a maximum of 32KB (including any necessary encoding) which imo is severly limited. (source: )
Comment 3 Maciej Stachowiak 2010-03-14 13:15:15 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.