source: draft-ietf-httpbis/orig/rfc6266.html @ 2496

Last change on this file since 2496 was 1305, checked in by julian.reschke@…, 12 years ago

add RFC6266 to the specs folder, add link to published spec in "latest" draft, regen HTML

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html
File size: 50.5 KB
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="">
5      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6      <title>Use of the Content-Disposition&nbsp;Header&nbsp;Field
7         in the Hypertext&nbsp;Transfer&nbsp;Protocol&nbsp;(HTTP)
8      </title><style type="text/css" title="Xml2Rfc (sans serif)">
9a {
10  text-decoration: none;
12a.smpl {
13  color: black;
15a:hover {
16  text-decoration: underline;
18a:active {
19  text-decoration: underline;
21address {
22  margin-top: 1em;
23  margin-left: 2em;
24  font-style: normal;
26blockquote {
27  border-style: solid;
28  border-color: gray;
29  border-width: 0 0 0 .25em;
30  font-style: italic;
31  padding-left: 0.5em;
33body {
34  color: black;
35  font-family: verdana, helvetica, arial, sans-serif;
36  font-size: 10pt;
38cite {
39  font-style: normal;
41div.note {
42  margin-left: 2em;
44dd {
45  margin-right: 2em;
47dl {
48  margin-left: 2em;
51ul.empty {
52  list-style-type: none;
54ul.empty li {
55  margin-top: .5em;
57dl p {
58  margin-left: 0em;
60dt {
61  margin-top: .5em;
63h1 {
64  font-size: 14pt;
65  line-height: 21pt;
66  page-break-after: avoid;
67} {
69  page-break-before: always;
71h1 a {
72  color: #333333;
74h2 {
75  font-size: 12pt;
76  line-height: 15pt;
77  page-break-after: avoid;
79h3, h4, h5, h6 {
80  font-size: 10pt;
81  page-break-after: avoid;
83h2 a, h3 a, h4 a, h5 a, h6 a {
84  color: black;
86img {
87  margin-left: 3em;
89li {
90  margin-left: 2em;
91  margin-right: 2em;
93ol {
94  margin-left: 2em;
95  margin-right: 2em;
96} {
98  list-style-type: lower-alpha;
99} {
101  list-style-type: upper-alpha;
103ol p {
104  margin-left: 0em;
106p {
107  margin-left: 2em;
108  margin-right: 2em;
110pre {
111  margin-left: 3em;
112  background-color: lightyellow;
113  padding: .25em;
115pre.text2 {
116  border-style: dotted;
117  border-width: 1px;
118  background-color: #f0f0f0;
119  width: 69em;
121pre.inline {
122  background-color: white;
123  padding: 0em;
125pre.text {
126  border-style: dotted;
127  border-width: 1px;
128  background-color: #f8f8f8;
129  width: 69em;
131pre.drawing {
132  border-style: solid;
133  border-width: 1px;
134  background-color: #f8f8f8;
135  padding: 2em;
137table {
138  margin-left: 2em;
140table.header {
141  border-spacing: 1px;
142  width: 95%;
143  font-size: 10pt;
144  color: white;
145} {
147  vertical-align: top;
149td.topnowrap {
150  vertical-align: top;
151  white-space: nowrap;
153table.header td {
154  background-color: gray;
155  width: 50%;
157table.header a {
158  color: white;
160td.reference {
161  vertical-align: top;
162  white-space: nowrap;
163  padding-right: 1em;
165thead {
166  display:table-header-group;
168ul.toc, ul.toc ul {
169  list-style: none;
170  margin-left: 1.5em;
171  margin-right: 0em;
172  padding-left: 0em;
174ul.toc li {
175  line-height: 150%;
176  font-weight: bold;
177  font-size: 10pt;
178  margin-left: 0em;
179  margin-right: 0em;
181ul.toc li li {
182  line-height: normal;
183  font-weight: normal;
184  font-size: 9pt;
185  margin-left: 0em;
186  margin-right: 0em;
188li.excluded {
189  font-size: 0pt;
191ul p {
192  margin-left: 0em;
194.bcp14 {
195  font-style: normal;
196  text-transform: lowercase;
197  font-variant: small-caps;
199blockquote > * .bcp14 {
200  font-style: italic;
202.comment {
203  background-color: yellow;
204} {
206  text-align: center;
208.error {
209  color: red;
210  font-style: italic;
211  font-weight: bold;
213.figure {
214  font-weight: bold;
215  text-align: center;
216  font-size: 9pt;
218.filename {
219  color: #333333;
220  font-weight: bold;
221  font-size: 12pt;
222  line-height: 21pt;
223  text-align: center;
225.fn {
226  font-weight: bold;
228.hidden {
229  display: none;
231.left {
232  text-align: left;
234.right {
235  text-align: right;
237.title {
238  color: #990000;
239  font-size: 18pt;
240  line-height: 18pt;
241  font-weight: bold;
242  text-align: center;
243  margin-top: 36pt;
245.vcardline {
246  display: block;
248.warning {
249  font-size: 14pt;
250  background-color: yellow;
254@media print {
255  .noprint {
256    display: none;
257  }
259  a {
260    color: black;
261    text-decoration: none;
262  }
264  table.header {
265    width: 90%;
266  }
268  td.header {
269    width: 50%;
270    color: black;
271    background-color: white;
272    vertical-align: top;
273    font-size: 12pt;
274  }
276  ul.toc a::after {
277    content: leader('.') target-counter(attr(href), page);
278  }
280  ul.ind li li a {
281    content: target-counter(attr(href), page);
282  }
284  .print2col {
285    column-count: 2;
286    -moz-column-count: 2;
287    column-fill: auto;
288  }
291@page {
292  @top-left {
293       content: "RFC 6266";
294  }
295  @top-right {
296       content: "June 2011";
297  }
298  @top-center {
299       content: "Content-Disposition in HTTP";
300  }
301  @bottom-left {
302       content: "Reschke";
303  }
304  @bottom-center {
305       content: "Standards Track";
306  }
307  @bottom-right {
308       content: "[Page " counter(page) "]";
309  }
312@page:first {
313    @top-left {
314      content: normal;
315    }
316    @top-right {
317      content: normal;
318    }
319    @top-center {
320      content: normal;
321    }
323</style><link rel="Contents" href="#rfc.toc">
324      <link rel="Author" href="#rfc.authors">
325      <link rel="Copyright" href="#rfc.copyrightnotice">
326      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
327      <link rel="Chapter" title="2 Notational Conventions" href="#rfc.section.2">
328      <link rel="Chapter" title="3 Conformance and Error Handling" href="#rfc.section.3">
329      <link rel="Chapter" title="4 Header Field Definition" href="#rfc.section.4">
330      <link rel="Chapter" title="5 Examples" href="#rfc.section.5">
331      <link rel="Chapter" title="6 Internationalization Considerations" href="#rfc.section.6">
332      <link rel="Chapter" title="7 Security Considerations" href="#rfc.section.7">
333      <link rel="Chapter" title="8 IANA Considerations" href="#rfc.section.8">
334      <link rel="Chapter" title="9 Acknowledgements" href="#rfc.section.9">
335      <link rel="Chapter" href="#rfc.section.10" title="10 References">
336      <link rel="Appendix" title="A Changes from the RFC 2616 Definition" href="#rfc.section.A">
337      <link rel="Appendix" title="B Differences Compared to RFC 2183" href="#rfc.section.B">
338      <link rel="Appendix" title="C Alternative Approaches to Internationalization" href="#rfc.section.C">
339      <link rel="Appendix" title="D Advice on Generating Content-Disposition Header Fields" href="#rfc.section.D">
340      <link rel="Alternate" title="Authorative ASCII Version" href="">
341      <link rel="Help" title="RFC-Editor's Status Page" href="">
342      <link rel="Help" title="Additional Information on" href="">
343      <meta name="generator" content=", Revision 1.550, 2011-05-30 14:02:12, XSLT vendor: SAXON 8.9 from Saxonica">
344      <meta name="keywords" content="HTTP, Hypertext Transfer Protocol, Content-Disposition, filename, attachment, inline">
345      <link rel="schema.dct" href="">
346      <meta name="dct.creator" content="Reschke, J. F.">
347      <meta name="dct.identifier" content="urn:ietf:rfc:6266">
348      <meta name="dct.issued" scheme="ISO8601" content="2011-06">
349      <meta name="dct.abstract" content="RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects.">
350      <meta name="dct.isPartOf" content="urn:issn:2070-1721">
351      <meta name="description" content="RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects.">
352   </head>
353   <body>
354      <table class="header">
355         <tbody>
356            <tr>
357               <td class="left">Internet Engineering Task Force (IETF)</td>
358               <td class="right">J. Reschke</td>
359            </tr>
360            <tr>
361               <td class="left">Request for Comments: 6266</td>
362               <td class="right">greenbytes</td>
363            </tr>
364            <tr>
365               <td class="left">Updates: <a href="">2616</a></td>
366               <td class="right">June 2011</td>
367            </tr>
368            <tr>
369               <td class="left">Category: Standards Track</td>
370               <td class="right"></td>
371            </tr>
372            <tr>
373               <td class="left">ISSN: 2070-1721</td>
374               <td class="right"></td>
375            </tr>
376         </tbody>
377      </table>
378      <p class="title">Use of the Content-Disposition&nbsp;Header&nbsp;Field in the Hypertext&nbsp;Transfer&nbsp;Protocol&nbsp;(HTTP)</p>
379      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
380      <p>RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard.
381         This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization
382         aspects.
383      </p>
384      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
385      <p>This is an Internet Standards Track document.</p>
386      <p>This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community.
387         It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further
388         information on Internet Standards is available in Section 2 of RFC 5741.
389      </p>
390      <p>Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at <a href=""></a>.
391      </p>
392      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
393      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
394      <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href=""></a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
395         and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
396         text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
397         BSD License.
398      </p>
399      <hr class="noprint">
400      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
401      <ul class="toc">
402         <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a></li>
403         <li>2.&nbsp;&nbsp;&nbsp;<a href="#notational.conventions">Notational Conventions</a></li>
404         <li>3.&nbsp;&nbsp;&nbsp;<a href="#conformance.and.error.handling">Conformance and Error Handling</a></li>
405         <li>4.&nbsp;&nbsp;&nbsp;<a href="#header.field.definition">Header Field Definition</a><ul>
406               <li>4.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.1">Grammar</a></li>
407               <li>4.2&nbsp;&nbsp;&nbsp;<a href="#disposition.type">Disposition Type</a></li>
408               <li>4.3&nbsp;&nbsp;&nbsp;<a href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></li>
409               <li>4.4&nbsp;&nbsp;&nbsp;<a href="#disposition.parameter.extensions">Disposition Parameter: Extensions</a></li>
410               <li>4.5&nbsp;&nbsp;&nbsp;<a href="#extensibility">Extensibility</a></li>
411            </ul>
412         </li>
413         <li>5.&nbsp;&nbsp;&nbsp;<a href="#examples">Examples</a></li>
414         <li>6.&nbsp;&nbsp;&nbsp;<a href="#i18n">Internationalization Considerations</a></li>
415         <li>7.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
416         <li>8.&nbsp;&nbsp;&nbsp;<a href="#iana.considerations">IANA Considerations</a><ul>
417               <li>8.1&nbsp;&nbsp;&nbsp;<a href="#registry">Registry for Disposition Values and Parameters</a></li>
418               <li>8.2&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
419            </ul>
420         </li>
421         <li>9.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9">Acknowledgements</a></li>
422         <li>10.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
423               <li>10.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
424               <li>10.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
425            </ul>
426         </li>
427         <li><a href="#rfc.authors">Author's Address</a></li>
428         <li>A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc2616">Changes from the RFC 2616 Definition</a></li>
429         <li>B.&nbsp;&nbsp;&nbsp;<a href="">Differences Compared to RFC 2183</a></li>
430         <li>C.&nbsp;&nbsp;&nbsp;<a href="#alternatives">Alternative Approaches to Internationalization</a><ul>
431               <li>C.1&nbsp;&nbsp;&nbsp;<a href="#alternatives.rfc2047">RFC 2047 Encoding</a></li>
432               <li>C.2&nbsp;&nbsp;&nbsp;<a href="#alternatives.percent">Percent Encoding</a></li>
433               <li>C.3&nbsp;&nbsp;&nbsp;<a href="#alternatives.sniff">Encoding Sniffing</a></li>
434            </ul>
435         </li>
436         <li>D.&nbsp;&nbsp;&nbsp;<a href="#advice.generating">Advice on Generating Content-Disposition Header Fields</a></li>
437      </ul>
438      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
439      <p id="rfc.section.1.p.1">RFC 2616 defines the Content-Disposition response header field (<a href="">Section 19.5.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>) but points out that it is not part of the HTTP/1.1 Standard (<a href="" id="rfc.xref.RFC2616.2">Section 15.5</a>):
440      </p>
441      <blockquote id="rfc.section.1.p.2" cite="">
442         <p>Content-Disposition is not part of the HTTP standard, but since it is widely implemented, we are documenting its use and risks
443            for implementers.
444         </p>
445      </blockquote>
446      <p id="rfc.section.1.p.3">This specification takes over the definition and registration of Content-Disposition, as used in HTTP. Based on interoperability
447         testing with existing user agents (UAs), it fully defines a profile of the features defined in the Multipurpose Internet Mail
448         Extensions (MIME) variant (<a href="#RFC2183" id="rfc.xref.RFC2183.1"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>) of the header field, and also clarifies internationalization aspects.
449      </p>
450      <div class="note" id="rfc.section.1.p.4">
451         <p> <b>Note:</b> This document does not apply to Content-Disposition header fields appearing in payload bodies transmitted over HTTP, such
452            as when using the media type "multipart/form-data" (<a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>).
453         </p>
454      </div>
455      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="notational.conventions" href="#notational.conventions">Notational Conventions</a></h1>
456      <p id="rfc.section.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
457         in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
458      </p>
459      <p id="rfc.section.2.p.2">This specification uses the augmented BNF (ABNF) notation defined in <a href="">Section 2.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, including its rules for implied linear whitespace (LWS).
460      </p>
461      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="conformance.and.error.handling" href="#conformance.and.error.handling">Conformance and Error Handling</a></h1>
462      <p id="rfc.section.3.p.1">This specification defines conformance criteria for both senders (usually, HTTP origin servers) and recipients (usually, HTTP
463         user agents) of the Content-Disposition header field. An implementation is considered conformant if it complies with all of
464         the requirements associated with its role.
465      </p>
466      <p id="rfc.section.3.p.2">This specification also defines certain forms of the header field value to be invalid, using both ABNF and prose requirements
467         (<a href="#header.field.definition" id="rfc.xref.header.field.definition.1" title="Header Field Definition">Section&nbsp;4</a>), but it does not define special handling of these invalid field values.
468      </p>
469      <p id="rfc.section.3.p.3">Senders <em class="bcp14">MUST NOT</em> generate Content-Disposition header fields that are invalid.
470      </p>
471      <p id="rfc.section.3.p.4">Recipients <em class="bcp14">MAY</em> take steps to recover a usable field value from an invalid header field, but <em class="bcp14">SHOULD NOT</em> reject the message outright, unless this is explicitly desirable behavior (e.g., the implementation is a validator). As such,
472         the default handling of invalid fields is to ignore them.
473      </p>
474      <div id="rfc.iref.h.1"></div>
475      <div id="rfc.iref.c.1"></div>
476      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="header.field.definition" href="#header.field.definition">Header Field Definition</a></h1>
477      <p id="rfc.section.4.p.1">The Content-Disposition response header field is used to convey additional information about how to process the response payload,
478         and also can be used to attach additional metadata, such as the filename to use when saving the response payload locally.
479      </p>
480      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;Grammar
481      </h2>
482      <div id="rfc.figure.u.1"></div><pre class="inline">  content-disposition = "Content-Disposition" ":"
483                         disposition-type *( ";" disposition-parm )
485  disposition-type    = "inline" | "attachment" | disp-ext-type
486                      ; case-insensitive
487  disp-ext-type       = token
489  disposition-parm    = filename-parm | disp-ext-parm
491  filename-parm       = "filename" "=" value
492                      | "filename*" "=" ext-value
494  disp-ext-parm       = token "=" value
495                      | ext-token "=" ext-value
496  ext-token           = &lt;the characters in token, followed by "*"&gt;
497</pre><div id="rfc.figure.u.2"></div>
498      <p>Defined in <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>:
499      </p>  <pre class="inline">  token         = &lt;token, defined in <a href="#RFC2616" id="rfc.xref.RFC2616.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="">Section 2.2</a>&gt;
500  quoted-string = &lt;quoted-string, defined in <a href="#RFC2616" id="rfc.xref.RFC2616.6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="">Section 2.2</a>&gt;
501  value         = &lt;value, defined in <a href="#RFC2616" id="rfc.xref.RFC2616.7"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="">Section 3.6</a>&gt;
502                ; token | quoted-string
504</pre><div id="rfc.figure.u.3"></div>
505      <p>Defined in <a href="#RFC5987" id="rfc.xref.RFC5987.1"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>:
506      </p>  <pre class="inline">  ext-value   = &lt;ext-value, defined in <a href="#RFC5987" id="rfc.xref.RFC5987.2"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>, <a href="">Section 3.2</a>&gt;
507</pre><p id="rfc.section.4.1.p.4">Content-Disposition header field values with multiple instances of the same parameter name are invalid.</p>
508      <p id="rfc.section.4.1.p.5">Note that due to the rules for implied linear whitespace (<a href="">Section 2.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.8"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>), <em class="bcp14">OPTIONAL</em> whitespace can appear between words (token or quoted-string) and separator characters.
509      </p>
510      <p id="rfc.section.4.1.p.6">Furthermore, note that the format used for ext-value allows specifying a natural language (e.g., "en"); this is of limited
511         use for filenames and is likely to be ignored by recipients.
512      </p>
513      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="disposition.type" href="#disposition.type">Disposition Type</a></h2>
514      <p id="rfc.section.4.2.p.1">If the disposition type matches "attachment" (case-insensitively), this indicates that the recipient should prompt the user
515         to save the response locally, rather than process it normally (as per its media type).
516      </p>
517      <p id="rfc.section.4.2.p.2">On the other hand, if it matches "inline" (case-insensitively), this implies default processing. Therefore, the disposition
518         type "inline" is only useful when it is augmented with additional parameters, such as the filename (see below).
519      </p>
520      <p id="rfc.section.4.2.p.3">Unknown or unhandled disposition types <em class="bcp14">SHOULD</em> be handled by recipients the same way as "attachment" (see also <a href="#RFC2183" id="rfc.xref.RFC2183.2"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>, <a href="">Section 2.8</a>).
521      </p>
522      <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a id="disposition.parameter.filename" href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></h2>
523      <p id="rfc.section.4.3.p.1">The parameters "filename" and "filename*", to be matched case-insensitively, provide information on how to construct a filename
524         for storing the message payload.
525      </p>
526      <p id="rfc.section.4.3.p.2">Depending on the disposition type, this information might be used right away (in the "save as..." interaction caused for the
527         "attachment" disposition type), or later on (for instance, when the user decides to save the contents of the current page
528         being displayed).
529      </p>
530      <p id="rfc.section.4.3.p.3">The parameters "filename" and "filename*" differ only in that "filename*" uses the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.3"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>, allowing the use of characters not present in the ISO-8859-1 character set (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No.&nbsp;1">[ISO-8859-1]</cite></a>).
531      </p>
532      <p id="rfc.section.4.3.p.4">Many user agent implementations predating this specification do not understand the "filename*" parameter. Therefore, when
533         both "filename" and "filename*" are present in a single header field value, recipients <em class="bcp14">SHOULD</em> pick "filename*" and ignore "filename". This way, senders can avoid special-casing specific user agents by sending both the
534         more expressive "filename*" parameter, and the "filename" parameter as fallback for legacy recipients (see <a href="#examples" title="Examples">Section&nbsp;5</a> for an example).
535      </p>
536      <p id="rfc.section.4.3.p.5">It is essential that recipients treat the specified filename as advisory only, and thus be very careful in extracting the
537         desired information. In particular:
538      </p>
539      <ul>
540         <li>
541            <p>Recipients <em class="bcp14">MUST NOT</em> be able to write into any location other than one to which they are specifically entitled. To illustrate the problem, consider
542               the consequences of being able to overwrite well-known system locations (such as "/etc/passwd"). One strategy to achieve this
543               is to never trust folder name information in the filename parameter, for instance by stripping all but the last path segment
544               and only considering the actual filename (where 'path segments' are the components of the field value delimited by the path
545               separator characters "\" and "/").
546            </p>
547         </li>
548         <li>
549            <p>Many platforms do not use Internet Media Types (<a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>) to hold type information in the file system, but rely on filename extensions instead. Trusting the server-provided file
550               extension could introduce a privilege escalation when the saved file is later opened (consider ".exe"). Thus, recipients that
551               make use of file extensions to determine the media type <em class="bcp14">MUST</em> ensure that a file extension is used that is safe, optimally matching the media type of the received payload.
552            </p>
553         </li>
554         <li>
555            <p>Recipients <em class="bcp14">SHOULD</em> strip or replace character sequences that are known to cause confusion both in user interfaces and in filenames, such as control
556               characters and leading and trailing whitespace.
557            </p>
558         </li>
559         <li>
560            <p>Other aspects recipients need to be aware of are names that have a special meaning in the file system or in shell commands,
561               such as "." and "..", "~", "|", and also device names. Recipients <em class="bcp14">SHOULD</em> ignore or substitute names like these.
562            </p>
563         </li>
564      </ul>
565      <div class="note" id="rfc.section.4.3.p.6">
566         <p> <b>Note:</b> Many user agents do not properly handle the escape character "\" when using the quoted-string form. Furthermore, some user
567            agents erroneously try to perform unescaping of "percent" escapes (see <a href="#alternatives.percent" title="Percent Encoding">Appendix&nbsp;C.2</a>), and thus might misinterpret filenames containing the percent character followed by two hex digits.
568         </p>
569      </div>
570      <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a id="disposition.parameter.extensions" href="#disposition.parameter.extensions">Disposition Parameter: Extensions</a></h2>
571      <p id="rfc.section.4.4.p.1">To enable future extensions, recipients <em class="bcp14">SHOULD</em> ignore unrecognized parameters (see also <a href="#RFC2183" id="rfc.xref.RFC2183.3"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>, <a href="">Section 2.8</a>).
572      </p>
573      <h2 id="rfc.section.4.5"><a href="#rfc.section.4.5">4.5</a>&nbsp;<a id="extensibility" href="#extensibility">Extensibility</a></h2>
574      <p id="rfc.section.4.5.p.1">Note that <a href="">Section 9</a> of <a href="#RFC2183" id="rfc.xref.RFC2183.4"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a> defines IANA registries both for disposition types and disposition parameters. This registry is shared by different protocols
575         using Content-Disposition, such as MIME and HTTP. Therefore, not all registered values may make sense in the context of HTTP.
576      </p>
577      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="examples" href="#examples">Examples</a></h1>
578      <div id="rfc.figure.u.4"></div>
579      <p>Direct the UA to show "save as" dialog, with a filename of "example.html":</p>  <pre class="text">Content-Disposition: Attachment; filename=example.html
580</pre><div id="rfc.figure.u.5"></div>
581      <p>Direct the UA to behave as if the Content-Disposition header field wasn't present, but to remember the filename "an example.html"
582         for a subsequent save operation:
583      </p>  <pre class="text">Content-Disposition: INLINE; FILENAME= "an example.html"
584</pre>  <p>Note: This uses the quoted-string form so that the space character can be included.</p>
585      <div id="rfc.figure.u.6"></div>
586      <p>Direct the UA to show "save as" dialog, with a filename containing the Unicode character U+20AC (EURO SIGN):</p>  <pre class="text">Content-Disposition: attachment;
587                     filename*= UTF-8''<b>%e2%82%ac</b>%20rates
588</pre>  <p>Here, the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.4"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a> is also used to encode the non-ISO-8859-1 character.
589      </p>
590      <div id="rfc.figure.u.7"></div>
591      <p>This example is the same as the one above, but adding the "filename" parameter for compatibility with user agents not implementing
592         RFC&nbsp;5987:
593      </p>  <pre class="text">Content-Disposition: attachment;
594                     filename="EURO rates";
595                     filename*=utf-8''<b>%e2%82%ac</b>%20rates
596</pre>  <p>Note: Those user agents that do not support the RFC 5987 encoding ignore "filename*" when it occurs after "filename".</p>
597      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="i18n" href="#i18n">Internationalization Considerations</a></h1>
598      <p id="rfc.section.6.p.1">The "filename*" parameter (<a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;4.3</a>), using the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.5"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>, allows the server to transmit characters outside the ISO-8859-1 character set, and also to optionally specify the language
599         in use.
600      </p>
601      <p id="rfc.section.6.p.2">Future parameters might also require internationalization, in which case the same encoding can be used.</p>
602      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
603      <p id="rfc.section.7.p.1">Using server-supplied information for constructing local filenames introduces many risks. These are summarized in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;4.3</a>.
604      </p>
605      <p id="rfc.section.7.p.2">Furthermore, implementers ought to be aware of the security considerations applying to HTTP (see <a href="">Section 15</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.9"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>), and also the parameter encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.6"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a> (see <a href="" id="rfc.xref.RFC5987.7">Section 5</a>).
606      </p>
607      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="iana.considerations" href="#iana.considerations">IANA Considerations</a></h1>
608      <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="registry" href="#registry">Registry for Disposition Values and Parameters</a></h2>
609      <p id="rfc.section.8.1.p.1">This specification does not introduce any changes to the registration procedures for disposition values and parameters that
610         are defined in <a href="">Section 9</a> of <a href="#RFC2183" id="rfc.xref.RFC2183.5"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>.
611      </p>
612      <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
613      <p id="rfc.section.8.2.p.1">This document updates the definition of the Content-Disposition HTTP header field in the permanent HTTP header field registry
614         (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>).
615      </p>
616      <p id="rfc.section.8.2.p.2"> </p>
617      <dl>
618         <dt>Header field name:</dt>
619         <dd>Content-Disposition</dd>
620         <dt>Applicable protocol:</dt>
621         <dd>http</dd>
622         <dt>Status:</dt>
623         <dd>standard</dd>
624         <dt>Author/Change controller:</dt>
625         <dd>IETF</dd>
626         <dt>Specification document:</dt>
627         <dd>this specification (<a href="#header.field.definition" id="rfc.xref.header.field.definition.2" title="Header Field Definition">Section&nbsp;4</a>)
628         </dd>
629         <dt>Related information:</dt>
630         <dd>none</dd>
631      </dl>
632      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;Acknowledgements
633      </h1>
634      <p id="rfc.section.9.p.1">Thanks to Adam Barth, Rolf Eike Beer, Stewart Bryant, Bjoern Hoehrmann, Alfred Hoenes, Roar Lauritzsen, Alexey Melnikov, Henrik
635         Nordstrom, and Mark Nottingham for their valuable feedback.
636      </p>
637      <h1 id="rfc.references"><a id="rfc.section.10" href="#rfc.section.10">10.</a> References
638      </h1>
639      <h2 id="rfc.references.1"><a href="#rfc.section.10.1" id="rfc.section.10.1">10.1</a> Normative References
640      </h2>
641      <table>       
642         <tr>
643            <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td>
644            <td class="top">International Organization for Standardization, “Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No.&nbsp;1”, ISO/IEC&nbsp;8859-1:1998, 1998.</td>
645         </tr>
646         <tr>
647            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
648            <td class="top"><a href="" title="Harvard University">Bradner, S.</a>, “<a href="">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
649            </td>
650         </tr>
651         <tr>
652            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
653            <td class="top"><a href="" title="University of California, Irvine">Fielding, R.</a>, <a href="" title="W3C">Gettys, J.</a>, <a href="" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="" title="Xerox Corporation">Masinter, L.</a>, <a href="" title="Microsoft Corporation">Leach, P.</a>, and <a href="" title="W3C">T. Berners-Lee</a>, “<a href="">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
654            </td>
655         </tr>
656         <tr>
657            <td class="reference"><b id="RFC5987">[RFC5987]</b></td>
658            <td class="top"><a href="" title="greenbytes GmbH">Reschke, J.</a>, “<a href="">Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters</a>”, RFC&nbsp;5987, August&nbsp;2010.
659            </td>
660         </tr>
661      </table>
662      <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References
663      </h2>
664      <table>                 
665         <tr>
666            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
667            <td class="top"><a href="" title="Innosoft International, Inc.">Freed, N.</a> and <a href="" title="First Virtual Holdings">N. Borenstein</a>, “<a href="">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC&nbsp;2046, November&nbsp;1996.
668            </td>
669         </tr>
670         <tr>
671            <td class="reference"><b id="RFC2047">[RFC2047]</b></td>
672            <td class="top"><a href="" title="University of Tennessee">Moore, K.</a>, “<a href="">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</a>”, RFC&nbsp;2047, November&nbsp;1996.
673            </td>
674         </tr>
675         <tr>
676            <td class="reference"><b id="RFC2183">[RFC2183]</b></td>
677            <td class="top"><a href="" title="New Century Systems">Troost, R.</a>, <a href="" title="QUALCOMM Incorporated">Dorner, S.</a>, and <a href="" title="Department of Computer Science">K. Moore, Ed.</a>, “<a href="">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</a>”, RFC&nbsp;2183, August&nbsp;1997.
678            </td>
679         </tr>
680         <tr>
681            <td class="reference"><b id="RFC2231">[RFC2231]</b></td>
682            <td class="top"><a href="" title="Innosoft International, Inc.">Freed, N.</a> and <a href="" title="University of Tennessee">K. Moore</a>, “<a href="">MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations</a>”, RFC&nbsp;2231, November&nbsp;1997.
683            </td>
684         </tr>
685         <tr>
686            <td class="reference"><b id="RFC2388">[RFC2388]</b></td>
687            <td class="top"><a href="" title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="">Returning Values from Forms: multipart/form-data</a>”, RFC&nbsp;2388, August&nbsp;1998.
688            </td>
689         </tr>
690         <tr>
691            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
692            <td class="top"><a href="" title="Nine by Nine">Klyne, G.</a>, <a href="" title="BEA Systems">Nottingham, M.</a>, and <a href="" title="HP Labs">J. Mogul</a>, “<a href="">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
693            </td>
694         </tr>
695         <tr>
696            <td class="reference"><b id="RFC3986">[RFC3986]</b></td>
697            <td class="top"><a href="" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="" title="Day Software">Fielding, R.</a>, and <a href="" title="Adobe Systems Incorporated">L. Masinter</a>, “<a href="">Uniform Resource Identifier (URI): Generic Syntax</a>”, STD&nbsp;66, RFC&nbsp;3986, January&nbsp;2005.
698            </td>
699         </tr>
700         <tr>
701            <td class="reference"><b id="US-ASCII">[US-ASCII]</b></td>
702            <td class="top">American National Standards Institute, “Coded Character Set -- 7-bit American Standard Code for Information Interchange”, ANSI&nbsp;X3.4, 1986.</td>
703         </tr>
704      </table>
705      <div class="avoidbreak">
706         <h1 id="rfc.authors"><a href="#rfc.authors">Author's Address</a></h1>
707         <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span><span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline">Email: <a href=""><span class="email"></span></a></span><span class="vcardline">URI: <a href="" class="url"></a></span></address>
708      </div>
709      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="changes.from.rfc2616" href="#changes.from.rfc2616">Changes from the RFC 2616 Definition</a></h1>
710      <p id="rfc.section.A.p.1">Compared to <a href="">Section 19.5.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.10"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, the following normative changes reflecting actual implementations have been made:
711      </p>
712      <ul>
713         <li>According to RFC 2616, the disposition type "attachment" only applies to content of type "application/octet-stream". This
714            restriction has been removed, because recipients in practice do not check the content type, and it also discourages properly
715            declaring the media type.
716         </li>
717         <li>RFC 2616 only allows "quoted-string" for the filename parameter. This would be an exceptional parameter syntax, and also doesn't
718            reflect actual use.
719         </li>
720         <li>The definition for the disposition type "inline" (<a href="#RFC2183" id="rfc.xref.RFC2183.6"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>, <a href="">Section 2.1</a>) has been re-added with a suggestion for its processing.
721         </li>
722         <li>This specification requires support for the extended parameter encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.8"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>.
723         </li>
724      </ul>
725      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="" href="">Differences Compared to RFC 2183</a></h1>
726      <p id="rfc.section.B.p.1"> <a href="">Section 2</a> of <a href="#RFC2183" id="rfc.xref.RFC2183.7"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a> defines several additional disposition parameters: "creation-date", "modification-date", "quoted-date-time", and "size". The
727         majority of user agents do not implement these; thus, they have been omitted from this specification.
728      </p>
729      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="alternatives" href="#alternatives">Alternative Approaches to Internationalization</a></h1>
730      <p id="rfc.section.C.p.1">By default, HTTP header field parameters cannot carry characters outside the ISO-8859-1 (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.2"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No.&nbsp;1">[ISO-8859-1]</cite></a>) character encoding (see <a href="#RFC2616" id="rfc.xref.RFC2616.11"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="">Section 2.2</a>). For the "filename" parameter, this of course is an unacceptable restriction.
731      </p>
732      <p id="rfc.section.C.p.2">Unfortunately, user agent implementers have not managed to come up with an interoperable approach, although the IETF Standards
733         Track specifies exactly one solution (<a href="#RFC2231" id="rfc.xref.RFC2231.1"><cite title="MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations">[RFC2231]</cite></a>, clarified and profiled for HTTP in <a href="#RFC5987" id="rfc.xref.RFC5987.9"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>).
734      </p>
735      <p id="rfc.section.C.p.3">For completeness, the sections below describe the various approaches that have been tried, and explain how they are inferior
736         to the RFC&nbsp;5987 encoding used in this specification.
737      </p>
738      <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;<a id="alternatives.rfc2047" href="#alternatives.rfc2047">RFC 2047 Encoding</a></h2>
739      <p id="rfc.section.C.1.p.1">RFC 2047 defines an encoding mechanism for header fields, but this encoding is not supposed to be used for header field parameters
740         — see <a href="">Section 5</a> of <a href="#RFC2047" id="rfc.xref.RFC2047.1"><cite title="MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text">[RFC2047]</cite></a>:
741      </p>
742      <blockquote id="rfc.section.C.1.p.2" cite="">
743         <p>An 'encoded-word' MUST NOT appear within a 'quoted-string'.</p> 
744         <p>...</p> 
745         <p>An 'encoded-word' MUST NOT be used in parameter of a MIME Content-Type or Content-Disposition field, or in any structured
746            field body except within a 'comment' or 'phrase'.
747         </p>
748      </blockquote>
749      <p id="rfc.section.C.1.p.3">In practice, some user agents implement the encoding, some do not (exposing the encoded string to the user), and some get
750         confused by it.
751      </p>
752      <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;<a id="alternatives.percent" href="#alternatives.percent">Percent Encoding</a></h2>
753      <p id="rfc.section.C.2.p.1">Some user agents accept percent-encoded (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="">Section 2.1</a>) sequences of characters. The character encoding being used for decoding depends on various factors, including the encoding
754         of the referring page, the user agent's locale, its configuration, and also the actual value of the parameter.
755      </p>
756      <p id="rfc.section.C.2.p.2">In practice, this is hard to use because those user agents that do not support it will display the escaped character sequence
757         to the user. For those user agents that do implement this, it is difficult to predict what character encoding they actually
758         expect.
759      </p>
760      <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;<a id="alternatives.sniff" href="#alternatives.sniff">Encoding Sniffing</a></h2>
761      <p id="rfc.section.C.3.p.1">Some user agents inspect the value (which defaults to ISO-8859-1 for the quoted-string form) and switch to UTF-8 when it seems
762         to be more likely to be the correct interpretation.
763      </p>
764      <p id="rfc.section.C.3.p.2">As with the approaches above, this is not interoperable and, furthermore, risks misinterpreting the actual value.</p>
765      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="advice.generating" href="#advice.generating">Advice on Generating Content-Disposition Header Fields</a></h1>
766      <p id="rfc.section.D.p.1">To successfully interoperate with existing and future user agents, senders of the Content-Disposition header field are advised
767         to:
768      </p>
769      <p id="rfc.section.D.p.2"> </p>
770      <ul>
771         <li>Include a "filename" parameter when US-ASCII (<a href="#US-ASCII" id="rfc.xref.US-ASCII.1"><cite title="Coded Character Set -- 7-bit American Standard Code for Information Interchange">[US-ASCII]</cite></a>) is sufficiently expressive.
772         </li>
773         <li>Use the 'token' form of the filename parameter only when it does not contain disallowed characters (e.g., spaces); in such
774            cases, the quoted-string form should be used.
775         </li>
776         <li>Avoid including the percent character followed by two hexadecimal characters (e.g., %A9) in the filename parameter, since
777            some existing implementations consider it to be an escape character, while others will pass it through unchanged.
778         </li>
779         <li>Avoid including the "\" character in the quoted-string form of the filename parameter, as escaping is not implemented by some
780            user agents, and "\" can be considered an illegal path character.
781         </li>
782         <li>Avoid using non-ASCII characters in the filename parameter. Although most existing implementations will decode them as ISO‑8859‑1,
783            some will apply heuristics to detect UTF-8, and thus might fail on certain names.
784         </li>
785         <li>Include a "filename*" parameter where the desired filename cannot be expressed faithfully using the "filename" form. Note
786            that legacy user agents will not process this, and will fall back to using the "filename" parameter's content.
787         </li>
788         <li>When a "filename*" parameter is sent, to also generate a "filename" parameter as a fallback for user agents that do not support
789            the "filename*" form, if possible. This can be done by substituting characters with US-ASCII sequences (e.g., Unicode character
790            point U+00E4 (LATIN SMALL LETTER A WITH DIARESIS) by "ae"). Note that this may not be possible in some locales.
791         </li>
792         <li>When a "filename" parameter is included as a fallback (as per above), "filename" should occur first, due to parsing problems
793            in some existing implementations.
794         </li>
795         <li>Use UTF-8 as the encoding of the "filename*" parameter, when present, because at least one existing implementation only implements
796            that encoding.
797         </li>
798      </ul>
799      <p id="rfc.section.D.p.3">Note that this advice is based upon UA behavior at the time of writing, and might be superseded. At the time of publication
800         of this document, &lt;<a href=""></a>&gt; provides an overview of current levels of support in various implementations.
801      </p>
802   </body>
Note: See TracBrowser for help on using the repository browser.