[html5] r6494 - [e] (0) Update references for Content-Disposition from RFC2183 to RFC6266. Fixin [...]
whatwg at whatwg.org
whatwg at whatwg.org
Wed Aug 17 15:05:21 PDT 2011
Author: ianh
Date: 2011-08-17 15:05:20 -0700 (Wed, 17 Aug 2011)
New Revision: 6494
Modified:
complete.html
index
source
Log:
[e] (0) Update references for Content-Disposition from RFC2183 to RFC6266.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=13349
Modified: complete.html
===================================================================
--- complete.html 2011-08-17 21:51:02 UTC (rev 6493)
+++ complete.html 2011-08-17 22:05:20 UTC (rev 6494)
@@ -54771,7 +54771,7 @@
<p>The attribute can furthermore be given a value, to specify the
filename that user agents are to use when storing the resource in a
file system. This value can be overridden by the <code title=http-content-disposition>Content-Disposition</code> HTTP
- header's <code title="">filename</code> parameter. <a href=#refsRFC2183>[RFC2183]</a></p>
+ header's filename parameters. <a href=#refsRFC6266>[RFC6266]</a></p>
<p>In cross-origin situations, the <code title=attr-hyperlink-download><a href=#attr-hyperlink-download>download</a></code> attribute has to be
combined with the <code title=http-content-disposition>Content-Disposition</code> HTTP
@@ -54830,8 +54830,9 @@
<li><p>If the resource has a <code title=http-content-disposition>Content-Disposition</code> header, <!-- Content-Disposition: attachment; filename="" is always honoured, even cross-origin -->
that header specifies the <code title="">attachment</code>
- disposition type, and the header includes a <code title="">filename</code> parameter, then let <var title="">filename</var> have that value, and jump to the step
- labeled "sanitize" below. <a href=#refsRFC2183>[RFC2183]</a></li>
+ disposition type, and the header includes a filename parameter,
+ then let <var title="">filename</var> have the value specified by
+ the header, and jump to the step labeled "sanitize" below. <a href=#refsRFC6266>[RFC6266]</a></li>
<li><p>Let <var title="">resource origin</var> be the
<a href=#origin>origin</a> of the resource being downloaded.</li>
@@ -54848,9 +54849,8 @@
<li><p>If <var title="">trusted operation</var> is true and the <!-- Content-Disposition: *; filename="" overrides download="" for same-origin -->
resource has a <code title=http-content-disposition>Content-Disposition</code> header
- and that header includes a <code title="">filename</code>
- parameter, then let <var title="">filename</var> have that value,
- and jump to the step labeled "sanitize" below. <a href=#refsRFC2183>[RFC2183]</a></li>
+ and that header includes a filename parameter, then let <var title="">filename</var> have the value specified by the header, and
+ jump to the step labeled "sanitize" below. <a href=#refsRFC6266>[RFC6266]</a></li>
<li><p>If the download was not initiated from a
<a href=#hyperlink>hyperlink</a> created by an <code><a href=#the-a-element>a</a></code> or
@@ -54874,7 +54874,7 @@
and that header specifies the <code title="">attachment</code>
disposition type, let <var title="">filename</var> have the value
of <var title="">proposed filename</var>, and jump to the step
- labeled "sanitize" below. <a href=#refsRFC2183>[RFC2183]</a></li>
+ labeled "sanitize" below. <a href=#refsRFC6266>[RFC6266]</a></li>
<li><p><i>No proposed filename</i>: If <var title="">trusted <!-- fallback for same-origin resources or explicit downloads: use the resource's file name -->
operation</var> is true, or if the user indicated a preference for
@@ -101490,9 +101490,6 @@
<dd><cite><a href=http://tools.ietf.org/html/rfc2119>Key words for use in
RFCs to Indicate Requirement Levels</a></cite>, S. Bradner. IETF.</dd>
- <dt id=refsRFC2183>[RFC2183]</dt>
- <dd><cite><a href=http://tools.ietf.org/html/rfc2183>Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</a></cite>, R. Troost, S. Dorner, K. Moore. IETF.</dd>
-
<dt id=refsRFC2237>[RFC2237]</dt>
<dd><cite><a href=http://tools.ietf.org/html/rfc2237>Japanese Character
Encoding for Internet Messages</a></cite>, K. Tamaru. IETF.</dd>
@@ -101605,6 +101602,9 @@
for Global System for Mobile Communications (GSM) Short Message
Service (SMS)</a></cite>, E. Wilde, A. Vaha-Sipila. IETF.</dd>
+ <dt id=refsRFC6266>[RFC6266]</dt>
+ <dd><cite><a href=http://tools.ietf.org/html/rfc6266>Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</a></cite>, J. Reschke. IETF.</dd>
+
<dt id=refsSCSU>[SCSU]</dt>
<dd>(Non-normative) <cite><a href=http://www.unicode.org/reports/tr6/>UTR #6: A Standard
Compression Scheme For Unicode</a></cite>, M. Wolf, K. Whistler,
Modified: index
===================================================================
--- index 2011-08-17 21:51:02 UTC (rev 6493)
+++ index 2011-08-17 22:05:20 UTC (rev 6494)
@@ -54638,7 +54638,7 @@
<p>The attribute can furthermore be given a value, to specify the
filename that user agents are to use when storing the resource in a
file system. This value can be overridden by the <code title=http-content-disposition>Content-Disposition</code> HTTP
- header's <code title="">filename</code> parameter. <a href=#refsRFC2183>[RFC2183]</a></p>
+ header's filename parameters. <a href=#refsRFC6266>[RFC6266]</a></p>
<p>In cross-origin situations, the <code title=attr-hyperlink-download><a href=#attr-hyperlink-download>download</a></code> attribute has to be
combined with the <code title=http-content-disposition>Content-Disposition</code> HTTP
@@ -54697,8 +54697,9 @@
<li><p>If the resource has a <code title=http-content-disposition>Content-Disposition</code> header, <!-- Content-Disposition: attachment; filename="" is always honoured, even cross-origin -->
that header specifies the <code title="">attachment</code>
- disposition type, and the header includes a <code title="">filename</code> parameter, then let <var title="">filename</var> have that value, and jump to the step
- labeled "sanitize" below. <a href=#refsRFC2183>[RFC2183]</a></li>
+ disposition type, and the header includes a filename parameter,
+ then let <var title="">filename</var> have the value specified by
+ the header, and jump to the step labeled "sanitize" below. <a href=#refsRFC6266>[RFC6266]</a></li>
<li><p>Let <var title="">resource origin</var> be the
<a href=#origin>origin</a> of the resource being downloaded.</li>
@@ -54715,9 +54716,8 @@
<li><p>If <var title="">trusted operation</var> is true and the <!-- Content-Disposition: *; filename="" overrides download="" for same-origin -->
resource has a <code title=http-content-disposition>Content-Disposition</code> header
- and that header includes a <code title="">filename</code>
- parameter, then let <var title="">filename</var> have that value,
- and jump to the step labeled "sanitize" below. <a href=#refsRFC2183>[RFC2183]</a></li>
+ and that header includes a filename parameter, then let <var title="">filename</var> have the value specified by the header, and
+ jump to the step labeled "sanitize" below. <a href=#refsRFC6266>[RFC6266]</a></li>
<li><p>If the download was not initiated from a
<a href=#hyperlink>hyperlink</a> created by an <code><a href=#the-a-element>a</a></code> or
@@ -54741,7 +54741,7 @@
and that header specifies the <code title="">attachment</code>
disposition type, let <var title="">filename</var> have the value
of <var title="">proposed filename</var>, and jump to the step
- labeled "sanitize" below. <a href=#refsRFC2183>[RFC2183]</a></li>
+ labeled "sanitize" below. <a href=#refsRFC6266>[RFC6266]</a></li>
<li><p><i>No proposed filename</i>: If <var title="">trusted <!-- fallback for same-origin resources or explicit downloads: use the resource's file name -->
operation</var> is true, or if the user indicated a preference for
@@ -97082,9 +97082,6 @@
<dd><cite><a href=http://tools.ietf.org/html/rfc2119>Key words for use in
RFCs to Indicate Requirement Levels</a></cite>, S. Bradner. IETF.</dd>
- <dt id=refsRFC2183>[RFC2183]</dt>
- <dd><cite><a href=http://tools.ietf.org/html/rfc2183>Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</a></cite>, R. Troost, S. Dorner, K. Moore. IETF.</dd>
-
<dt id=refsRFC2237>[RFC2237]</dt>
<dd><cite><a href=http://tools.ietf.org/html/rfc2237>Japanese Character
Encoding for Internet Messages</a></cite>, K. Tamaru. IETF.</dd>
@@ -97197,6 +97194,9 @@
for Global System for Mobile Communications (GSM) Short Message
Service (SMS)</a></cite>, E. Wilde, A. Vaha-Sipila. IETF.</dd>
+ <dt id=refsRFC6266>[RFC6266]</dt>
+ <dd><cite><a href=http://tools.ietf.org/html/rfc6266>Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</a></cite>, J. Reschke. IETF.</dd>
+
<dt id=refsSCSU>[SCSU]</dt>
<dd>(Non-normative) <cite><a href=http://www.unicode.org/reports/tr6/>UTR #6: A Standard
Compression Scheme For Unicode</a></cite>, M. Wolf, K. Whistler,
Modified: source
===================================================================
--- source 2011-08-17 21:51:02 UTC (rev 6493)
+++ source 2011-08-17 22:05:20 UTC (rev 6494)
@@ -61680,8 +61680,8 @@
filename that user agents are to use when storing the resource in a
file system. This value can be overridden by the <code
title="http-content-disposition">Content-Disposition</code> HTTP
- header's <code title="">filename</code> parameter. <a
- href="#refsRFC2183">[RFC2183]</a></p>
+ header's filename parameters. <a
+ href="#refsRFC6266">[RFC6266]</a></p>
<p>In cross-origin situations, the <code
title="attr-hyperlink-download">download</code> attribute has to be
@@ -61752,10 +61752,10 @@
<li><p>If the resource has a <code
title="http-content-disposition">Content-Disposition</code> header, <!-- Content-Disposition: attachment; filename="" is always honoured, even cross-origin -->
that header specifies the <code title="">attachment</code>
- disposition type, and the header includes a <code
- title="">filename</code> parameter, then let <var
- title="">filename</var> have that value, and jump to the step
- labeled "sanitize" below. <a href="#refsRFC2183">[RFC2183]</a></p></li>
+ disposition type, and the header includes a filename parameter,
+ then let <var title="">filename</var> have the value specified by
+ the header, and jump to the step labeled "sanitize" below. <a
+ href="#refsRFC6266">[RFC6266]</a></p></li>
<li><p>Let <var title="">resource origin</var> be the
<span>origin</span> of the resource being downloaded.</p></li>
@@ -61775,9 +61775,10 @@
<li><p>If <var title="">trusted operation</var> is true and the <!-- Content-Disposition: *; filename="" overrides download="" for same-origin -->
resource has a <code
title="http-content-disposition">Content-Disposition</code> header
- and that header includes a <code title="">filename</code>
- parameter, then let <var title="">filename</var> have that value,
- and jump to the step labeled "sanitize" below. <a href="#refsRFC2183">[RFC2183]</a></p></li>
+ and that header includes a filename parameter, then let <var
+ title="">filename</var> have the value specified by the header, and
+ jump to the step labeled "sanitize" below. <a
+ href="#refsRFC6266">[RFC6266]</a></p></li>
<li><p>If the download was not initiated from a
<span>hyperlink</span> created by an <code>a</code> or
@@ -61803,7 +61804,7 @@
and that header specifies the <code title="">attachment</code>
disposition type, let <var title="">filename</var> have the value
of <var title="">proposed filename</var>, and jump to the step
- labeled "sanitize" below. <a href="#refsRFC2183">[RFC2183]</a></p></li>
+ labeled "sanitize" below. <a href="#refsRFC6266">[RFC6266]</a></p></li>
<li><p><i>No proposed filename</i>: If <var title="">trusted <!-- fallback for same-origin resources or explicit downloads: use the resource's file name -->
operation</var> is true, or if the user indicated a preference for
@@ -115627,9 +115628,6 @@
<dd><cite><a href="http://tools.ietf.org/html/rfc2119">Key words for use in
RFCs to Indicate Requirement Levels</a></cite>, S. Bradner. IETF.</dd>
- <dt id="refsRFC2183">[RFC2183]</dt>
- <dd><cite><a href="http://tools.ietf.org/html/rfc2183">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</a></cite>, R. Troost, S. Dorner, K. Moore. IETF.</dd>
-
<dt id="refsRFC2237">[RFC2237]</dt>
<dd><cite><a href="http://tools.ietf.org/html/rfc2237">Japanese Character
Encoding for Internet Messages</a></cite>, K. Tamaru. IETF.</dd>
@@ -115758,6 +115756,9 @@
for Global System for Mobile Communications (GSM) Short Message
Service (SMS)</a></cite>, E. Wilde, A. Vaha-Sipila. IETF.</dd>
+ <dt id="refsRFC6266">[RFC6266]</dt>
+ <dd><cite><a href="http://tools.ietf.org/html/rfc6266">Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</a></cite>, J. Reschke. IETF.</dd>
+
<dt id="refsSCSU">[SCSU]</dt>
<dd>(Non-normative) <cite><a
href="http://www.unicode.org/reports/tr6/">UTR #6: A Standard
More information about the Commit-Watchers
mailing list