RFC Errata
Found 6 records.
Status: Verified (2)
RFC 2397, "The "data" URL scheme", August 1998
Source of RFC: Legacy
Errata ID: 2009
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alexander Gebel
Date Reported: 2010-01-18
Verifier Name: Alexey Melnikov
Date Verified: 2010-03-11
Section 4 says:
data:text/plain;charset=iso-8859-7,%be%fg%be
It should say:
data:text/plain;charset=iso-8859-7,%be%d3%be
Notes:
The given hex encoding "%fg" is incorrect, because there is no hexadecimal digit "g" ("f" is last). A correct hex encoding of any character is permissible here.
Errata ID: 2045
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Julian Reschke
Date Reported: 2010-02-17
Verifier Name: Alexey Melnikov
Date Verified: 2010-03-11
Section 3 says:
3. Syntax
dataurl := "data:" [ mediatype ] [ ";base64" ] "," data
mediatype := [ type "/" subtype ] *( ";" parameter )
data := *urlchar
parameter := attribute "=" value
where "urlchar" is imported from [RFC2396], and "type", "subtype",
"attribute" and "value" are the corresponding tokens from [RFC2045],
represented using URL escaped encoding of [RFC2396] as necessary.
It should say:
3. Syntax
dataurl := "data:" [ mediatype ] [ ";base64" ] "," data
mediatype := [ type "/" subtype ] *( ";" parameter )
data := *uric
parameter := attribute "=" value
where "uric" is imported from [RFC2396], and "type", "subtype",
"attribute" and "value" are the corresponding tokens from [RFC2045],
represented using URL escaped encoding of [RFC2396] as necessary.
Notes:
"urlchar" is not defined in RFC2396, but "uric" is (which I think is what was supposed to be used).
Status: Reported (1)
RFC 2397, "The "data" URL scheme", August 1998
Source of RFC: Legacy
Errata ID: 5923
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Richard Gibson
Date Reported: 2019-11-29
Section 3 says:
3. Syntax
dataurl := "data:" [ mediatype ] [ ";base64" ] "," data
mediatype := [ type "/" subtype ] *( ";" parameter )
data := *uric
parameter := attribute "=" value
where "uric" is imported from [RFC2396], and "type", "subtype",
"attribute" and "value" are the corresponding tokens from [RFC2045],
represented using URL escaped encoding of [RFC2396] as necessary.
Attribute values in [RFC2045] are allowed to be either represented as
tokens or as quoted strings. However, within a "data" URL, the
"quoted-string" representation would be awkward, since the quote mark
is itself not a valid urlchar. For this reason, parameter values
should use the URL Escaped encoding instead of quoted string if the
parameter values contain any "tspecial".
It should say:
3. Syntax
dataurl := "data:" [ mediatype ] [ ";base64" ] "," data
mediatype := [ type "/" subtype ] *( ";" parameter )
data := *uric
parameter := attribute "=" value
value := token
where "uric" is imported from [RFC2396], and "type", "subtype",
"attribute" and "token" are the corresponding syntax from [RFC2045],
with values represented using %xx escaped encoding of [RFC2396] as
necessary.
Parameter values in [RFC2045] are allowed to be either represented as
tokens or as quoted strings. However, within a "data" URL, the
"quoted-string" representation would be awkward, since the quote mark
is itself not a valid urlchar. For this reason, parameter values are
required to be represented as tokens and %xx encoding MUST be used for
"tspecials" characters within them.
Notes:
Section 3 is not clear about excluding the "quoted-string" production completely as opposed to permitting it through percent-encoding, resulting in ambiguity for interpretation of URLs such as "data:text/example;foo=%22bar%22,*baz*". But Section 5 refers to accepted changes that 'eliminate "quoted printable" as an encoding since it would not easily yield valid URLs without additional %xx encoding, which itself is sufficient', so it seems that the intent is to *replace* quoted-string and always interpret percent-encoded characters as content (i.e., that my example corresponds with `Content-Type: text/example; foo="\"bar\""` rather than `Content-Type: text/example;foo="bar").
Status: Held for Document Update (2)
RFC 2397, "The "data" URL scheme", August 1998
Source of RFC: Legacy
Errata ID: 3214
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Julian Reschke
Date Reported: 2012-05-06
Held for Document Update by: Barry Leiba
Section 3 says:
Attribute values in [RFC2045] are allowed to be either represented as tokens or as quoted strings. However, within a "data" URL, the "quoted-string" representation would be awkward, since the quote mark is itself not a valid urlchar. For this reason, parameter values should use the URL Escaped encoding instead of quoted string if the parameter values contain any "tspecial".
Notes:
This advice does not work when the character is a delimiter such as ";".
Example media type:
text/plain;foo="bar;charset=iso-8859-1";charset=UTF-8
...represented as-is in data uri:
data:text/plain;foo=%22bar;charset=iso-8859-1%22;charset=UTF-8,...
...but following the advice from Section 3:
data:text/plain;foo=bar;charset=iso-8859-1;charset=UTF-8,...
which makes the charset parameter ambiguous.
Proposal for document update:
1) Keep the text pointing out double quotes will look awkward.
2) Insist on them being handled as per RFC 2045, when present.
3) Either remove the last sentence (after checking whether it's done in practice), or clarify which additional non-token characters are allowed here.
Errata ID: 4124
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Xue Fuqiao
Date Reported: 2014-09-26
Held for Document Update by: Barry Leiba
Date Held: 2014-09-27
Section 2 says:
The <mediatype> is an Internet media type specification (with optional parameters.)
It should say:
The <mediatype> is an Internet media type specification (with optional parameters).
Notes:
Periods go inside parentheses only if an entire sentence is inside the parentheses.
Status: Rejected (1)
RFC 2397, "The "data" URL scheme", August 1998
Source of RFC: Legacy
Errata ID: 3360
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Lance E Sloan
Date Reported: 2012-09-20
Rejected by: Barry Leiba
Date Rejected: 2012-09-20
Throughout the document, when it says:
The "data" URL scheme
It should say:
The "data" URI scheme
Notes:
The text refers to "URL" throughout, but to be correct, these are actually URIs.
--VERIFIER NOTES--
"URI"s are first documented in RFC 2396, which was developed at the same time as RFC 2397. At the time the document that became 2397 was approved, "URL" was the correct term. While it's correct that "URI" is the preferred term now, "URL" is also correct, and is the term that was in use when this document was written. This is not an error in the document.