Skip to content
Permalink
Browse files

[e] (0) Update references for Content-Disposition from RFC2183 to RFC…

…6266.

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=13349

git-svn-id: http://svn.whatwg.org/webapps@6494 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Aug 17, 2011
1 parent 110251b commit 9314d347d4bc46b4813851d75113eee186e4a501
Showing with 34 additions and 33 deletions.
  1. +10 −10 complete.html
  2. +10 −10 index
  3. +14 −13 source
<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

<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>

<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
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
<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>
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,
20 index
<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

<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>

<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
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
<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>
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,
27 source
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
<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>
<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
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
<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>
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

0 comments on commit 9314d34

Please sign in to comment.
You can’t perform that action at this time.