source: draft-ietf-httpbis-content-disp/00/draft-ietf-httpbis-content-disp.html @ 2200

Last change on this file since 2200 was 986, checked in by julian.reschke@…, 13 years ago

Prepare submission of draft-ietf-httpbis-content-disp-00

File size: 56.0 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;
41dd {
42  margin-right: 2em;
44dl {
45  margin-left: 2em;
48ul.empty {
49  list-style-type: none;
51ul.empty li {
52  margin-top: .5em;
54dl p {
55  margin-left: 0em;
57dt {
58  margin-top: .5em;
60h1 {
61  font-size: 14pt;
62  line-height: 21pt;
63  page-break-after: avoid;
64} {
66  page-break-before: always;
68h1 a {
69  color: #333333;
71h2 {
72  font-size: 12pt;
73  line-height: 15pt;
74  page-break-after: avoid;
76h3, h4, h5, h6 {
77  font-size: 10pt;
78  page-break-after: avoid;
80h2 a, h3 a, h4 a, h5 a, h6 a {
81  color: black;
83img {
84  margin-left: 3em;
86li {
87  margin-left: 2em;
88  margin-right: 2em;
90ol {
91  margin-left: 2em;
92  margin-right: 2em;
94ol p {
95  margin-left: 0em;
97p {
98  margin-left: 2em;
99  margin-right: 2em;
101pre {
102  margin-left: 3em;
103  background-color: lightyellow;
104  padding: .25em;
106pre.text2 {
107  border-style: dotted;
108  border-width: 1px;
109  background-color: #f0f0f0;
110  width: 69em;
112pre.inline {
113  background-color: white;
114  padding: 0em;
116pre.text {
117  border-style: dotted;
118  border-width: 1px;
119  background-color: #f8f8f8;
120  width: 69em;
122pre.drawing {
123  border-style: solid;
124  border-width: 1px;
125  background-color: #f8f8f8;
126  padding: 2em;
128table {
129  margin-left: 2em;
130} {
132  vertical-align: top;
134table.full {
135  border-style: outset;
136  border-width: 1px;
138table.headers {
139  border-style: outset;
140  border-width: 1px;
141} td {
143  vertical-align: top;
145table.full td {
146  border-style: inset;
147  border-width: 1px;
148} th {
150  vertical-align: top;
152table.full th {
153  border-style: inset;
154  border-width: 1px;
156table.headers th {
157  border-style: none none inset none;
158  border-width: 1px;
160table.left {
161  margin-right: auto;
163table.right {
164  margin-left: auto;
165} {
167  margin-left: auto;
168  margin-right: auto;
170caption {
171  caption-side: bottom;
172  font-weight: bold;
173  font-size: 9pt;
174  margin-top: .5em;
177table.header {
178  border-spacing: 1px;
179  width: 95%;
180  font-size: 10pt;
181  color: white;
182} {
184  vertical-align: top;
186td.topnowrap {
187  vertical-align: top;
188  white-space: nowrap;
190table.header td {
191  background-color: gray;
192  width: 50%;
194table.header a {
195  color: white;
197td.reference {
198  vertical-align: top;
199  white-space: nowrap;
200  padding-right: 1em;
202thead {
203  display:table-header-group;
205ul.toc {
206  list-style: none;
207  margin-left: 1.5em;
208  margin-right: 0em;
209  padding-left: 0em;
211li.tocline0 {
212  line-height: 150%;
213  font-weight: bold;
214  font-size: 10pt;
215  margin-left: 0em;
216  margin-right: 0em;
218li.tocline1 {
219  line-height: normal;
220  font-weight: normal;
221  font-size: 9pt;
222  margin-left: 0em;
223  margin-right: 0em;
225li.tocline2 {
226  font-size: 0pt;
228ul p {
229  margin-left: 0em;
231ul.ind {
232  list-style: none;
233  margin-left: 1.5em;
234  margin-right: 0em;
235  padding-left: 0em;
236  page-break-before: avoid;
238li.indline0 {
239  font-weight: bold;
240  line-height: 200%;
241  margin-left: 0em;
242  margin-right: 0em;
244li.indline1 {
245  font-weight: normal;
246  line-height: 150%;
247  margin-left: 0em;
248  margin-right: 0em;
250.avoidbreak {
251  page-break-inside: avoid;
253.bcp14 {
254  font-style: normal;
255  text-transform: lowercase;
256  font-variant: small-caps;
258blockquote > * .bcp14 {
259  font-style: italic;
261.comment {
262  background-color: yellow;
263} {
265  text-align: center;
267.error {
268  color: red;
269  font-style: italic;
270  font-weight: bold;
272.figure {
273  font-weight: bold;
274  text-align: center;
275  font-size: 9pt;
277.filename {
278  color: #333333;
279  font-weight: bold;
280  font-size: 12pt;
281  line-height: 21pt;
282  text-align: center;
284.fn {
285  font-weight: bold;
287.hidden {
288  display: none;
290.left {
291  text-align: left;
293.right {
294  text-align: right;
296.title {
297  color: #990000;
298  font-size: 18pt;
299  line-height: 18pt;
300  font-weight: bold;
301  text-align: center;
302  margin-top: 36pt;
304.vcardline {
305  display: block;
307.warning {
308  font-size: 14pt;
309  background-color: yellow;
313@media print {
314  .noprint {
315    display: none;
316  }
318  a {
319    color: black;
320    text-decoration: none;
321  }
323  table.header {
324    width: 90%;
325  }
327  td.header {
328    width: 50%;
329    color: black;
330    background-color: white;
331    vertical-align: top;
332    font-size: 12pt;
333  }
335  ul.toc a::after {
336    content: leader('.') target-counter(attr(href), page);
337  }
339  a.iref {
340    content: target-counter(attr(href), page);
341  }
343  .print2col {
344    column-count: 2;
345    -moz-column-count: 2;
346    column-fill: auto;
347  }
350@page {
351  @top-left {
352       content: "Internet-Draft";
353  }
354  @top-right {
355       content: "September 2010";
356  }
357  @top-center {
358       content: "Content-Disposition in HTTP";
359  }
360  @bottom-left {
361       content: "Reschke";
362  }
363  @bottom-center {
364       content: "Standards Track";
365  }
366  @bottom-right {
367       content: "[Page " counter(page) "]";
368  }
371@page:first {
372    @top-left {
373      content: normal;
374    }
375    @top-right {
376      content: normal;
377    }
378    @top-center {
379      content: normal;
380    }
382</style><link rel="Contents" href="#rfc.toc">
383      <link rel="Author" href="#rfc.authors">
384      <link rel="Copyright" href="#rfc.copyrightnotice">
385      <link rel="Index" href="#rfc.index">
386      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
387      <link rel="Chapter" title="2 Notational Conventions" href="#rfc.section.2">
388      <link rel="Chapter" title="3 Header Field Definition" href="#rfc.section.3">
389      <link rel="Chapter" title="4 Examples" href="#rfc.section.4">
390      <link rel="Chapter" title="5 Internationalization Considerations" href="#rfc.section.5">
391      <link rel="Chapter" title="6 Security Considerations" href="#rfc.section.6">
392      <link rel="Chapter" title="7 IANA Considerations" href="#rfc.section.7">
393      <link rel="Chapter" title="8 Acknowledgements" href="#rfc.section.8">
394      <link rel="Chapter" href="#rfc.section.9" title="9 References">
395      <link rel="Appendix" title="A Changes from the RFC 2616 Definition" href="#rfc.section.A">
396      <link rel="Appendix" title="B Differences compared to RFC 2183" href="#rfc.section.B">
397      <link rel="Appendix" title="C Alternative Approaches to Internationalization" href="#rfc.section.C">
398      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
399      <meta name="generator" content=", Revision 1.522, 2010-08-31 15:02:33, XSLT vendor: SAXON 8.9 from Saxonica">
400      <link rel="schema.dct" href="">
401      <meta name="dct.creator" content="Reschke, J. F.">
402      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-00">
403      <meta name="dct.issued" scheme="ISO8601" content="2010-09-03">
404      <meta name="dct.abstract" content="HTTP/1.1 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.">
405      <meta name="description" content="HTTP/1.1 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.">
406   </head>
407   <body>
408      <table class="header">
409         <tbody>
410            <tr>
411               <td class="left">HTTPbis Working Group</td>
412               <td class="right">J. Reschke</td>
413            </tr>
414            <tr>
415               <td class="left">Internet-Draft</td>
416               <td class="right">greenbytes</td>
417            </tr>
418            <tr>
419               <td class="left">Updates: <a href="">2616</a> (if approved)
420               </td>
421               <td class="right">September 3, 2010</td>
422            </tr>
423            <tr>
424               <td class="left">Intended status: Standards Track</td>
425               <td class="right"></td>
426            </tr>
427            <tr>
428               <td class="left">Expires: March 7, 2011</td>
429               <td class="right"></td>
430            </tr>
431         </tbody>
432      </table>
433      <p class="title">Use of the Content-Disposition&nbsp;Header&nbsp;Field in the Hypertext&nbsp;Transfer&nbsp;Protocol&nbsp;(HTTP)<br><span class="filename">draft-ietf-httpbis-content-disp-00</span></p>
434      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
435      <p>HTTP/1.1 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard.
436         This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization
437         aspects.
438      </p>
439      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor before publication)</a></h1>
440      <p>This specification is expected to replace the definition of Content-Disposition in the HTTP/1.1 specification, as currently
441         revised by the IETF HTTPbis working group. See also &lt;<a href=""></a>&gt;.
442      </p> 
443      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list ( The current issues
444         list is at &lt;<a href=""></a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href=""></a>&gt;.
445      </p>   
446      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
447      <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
448      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
449         working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href=""></a>.
450      </p>
451      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
452         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
453         in progress”.
454      </p>
455      <p>This Internet-Draft will expire on March 7, 2011.</p>
456      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
457      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
458      <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
459         and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
460         text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
461         BSD License.
462      </p>
463      <hr class="noprint">
464      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
465      <ul class="toc">
466         <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a></li>
467         <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2">Notational Conventions</a></li>
468         <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#header.field.definition">Header Field Definition</a><ul class="toc">
469               <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.1">Grammar</a></li>
470               <li class="tocline1">3.2&nbsp;&nbsp;&nbsp;<a href="#disposition.type">Disposition Type</a></li>
471               <li class="tocline1">3.3&nbsp;&nbsp;&nbsp;<a href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></li>
472               <li class="tocline1">3.4&nbsp;&nbsp;&nbsp;<a href="#disposition.parameter.extensionsS">Disposition Parameter: Extensions</a></li>
473               <li class="tocline1">3.5&nbsp;&nbsp;&nbsp;<a href="#extensibility">Extensibility</a></li>
474            </ul>
475         </li>
476         <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4">Examples</a></li>
477         <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#i18n">Internationalization Considerations</a></li>
478         <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
479         <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#iana.considerations">IANA Considerations</a><ul class="toc">
480               <li class="tocline1">7.1&nbsp;&nbsp;&nbsp;<a href="#registry">Registry for Disposition Values and Parameter</a></li>
481               <li class="tocline1">7.2&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
482            </ul>
483         </li>
484         <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.8">Acknowledgements</a></li>
485         <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul class="toc">
486               <li class="tocline1">9.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
487               <li class="tocline1">9.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
488            </ul>
489         </li>
490         <li class="tocline0"><a href="#rfc.authors">Author's Address</a></li>
491         <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc2616">Changes from the RFC 2616 Definition</a></li>
492         <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="">Differences compared to RFC 2183</a></li>
493         <li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#alternatives">Alternative Approaches to Internationalization</a><ul class="toc">
494               <li class="tocline1">C.1&nbsp;&nbsp;&nbsp;<a href="#alternatives.rfc2047">RFC 2047 Encoding</a></li>
495               <li class="tocline1">C.2&nbsp;&nbsp;&nbsp;<a href="#alternatives.percent">Percent Encoding</a></li>
496               <li class="tocline1">C.3&nbsp;&nbsp;&nbsp;<a href="#alternatives.sniff">Encoding Sniffing</a></li>
497               <li class="tocline1">C.4&nbsp;&nbsp;&nbsp;<a href="#alternatives.implementations">Implementations</a></li>
498            </ul>
499         </li>
500         <li class="tocline0">D.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
501               <li class="tocline1">D.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since draft-reschke-rfc2183-in-http-00</a></li>
502               <li class="tocline1">D.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.2">Since draft-reschke-rfc2183-in-http-01</a></li>
503               <li class="tocline1">D.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.3">Since draft-reschke-rfc2183-in-http-02</a></li>
504               <li class="tocline1">D.4&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.4">Since draft-reschke-rfc2183-in-http-03</a></li>
505            </ul>
506         </li>
507         <li class="tocline0"><a href="#rfc.index">Index</a></li>
508      </ul>
509      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
510      <p id="rfc.section.1.p.1">HTTP/1.1 defines the Content-Disposition response header field in <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>):
511      </p>
512      <blockquote id="rfc.section.1.p.2" cite="">
513         <p>Content-Disposition is not part of the HTTP standard, but since it is widely implemented, we are documenting its use and risks
514            for implementers.
515         </p>
516      </blockquote>
517      <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
518         testing with existing User Agents, it fully defines a profile of the features defined in the Multipurpose Internet Mail Extensions
519         (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.
520      </p>
521      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;Notational Conventions
522      </h1>
523      <p id="rfc.section.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
524         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>.
525      </p>
526      <p id="rfc.section.2.p.2">This specification uses the augmented BNF 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 linear whitespace (LWS).
527      </p>
528      <div id="rfc.iref.h.1"></div>
529      <div id="rfc.iref.c.1"></div>
530      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.field.definition" href="#header.field.definition">Header Field Definition</a></h1>
531      <p id="rfc.section.3.p.1">The Content-Disposition response header field is used to convey additional information about how to process the response payload,
532         and also can be used to attach additional metadata, such as the filename.
533      </p>
534      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;Grammar
535      </h2>
536      <div id="rfc.figure.u.1"></div><pre class="inline">  content-disposition = "Content-Disposition" ":"
537                         disposition-type *( ";" disposition-parm )
539  disposition-type    = "inline" | "attachment" | disp-ext-type
540                      ; case-insensitive
541  disp-ext-type       = token
543  disposition-parm    = filename-parm | disp-ext-parm
545  filename-parm       = "filename" "=" value
546                      | "filename*" "=" ext-value
548  disp-ext-parm       = token "=" value
549                      | ext-token "=" ext-value
550  ext-token           = &lt;the characters in token, followed by "*"&gt;
551</pre><div id="rfc.figure.u.2"></div>
552      <p>Defined in <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>:
553      </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;
554  value       = &lt;value, defined in <a href="#RFC2616" id="rfc.xref.RFC2616.6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="">Section 3.6</a>&gt;
555</pre><div id="rfc.figure.u.3"></div>
556      <p>Defined in <a href="#RFC5987" id="rfc.xref.RFC5987.1"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>:
557      </p>  <pre class="inline">  ext-value   = &lt;ext-value, defined in <a href="#RFC5987" id="rfc.xref.RFC5987.2"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>, <a href="">Section 3.2</a>&gt;
558</pre><h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="disposition.type" href="#disposition.type">Disposition Type</a></h2>
559      <p id="rfc.section.3.2.p.1">If the disposition type matches "attachment" (case-insensitively), this indicates that the user agent should not display the
560         response, but directly enter a "save as..." dialog.
561      </p>
562      <p id="rfc.section.3.2.p.2">On the other hand, if it matches "inline" (case-insensitively), this implies default processing.</p>
563      <p id="rfc.section.3.2.p.3">Other disposition types <em class="bcp14">SHOULD</em> be handled 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>).
564      </p>
565      <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="disposition.parameter.filename" href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></h2>
566      <p id="rfc.section.3.3.p.1">The parameters "filename" and "filename*", to be matched case-insensitively, provide information on how to construct a filename
567         for storing the message payload.
568      </p>
569      <p id="rfc.section.3.3.p.2">Depending on the disposition type, this information might be used right away (in the "save as..." interaction caused for the
570         "attachment" disposition type), or later on (for instance, when the user decides to save the contents of the current page
571         being displayed).
572      </p>
573      <p id="rfc.section.3.3.p.3">"filename" and "filename*" behave the same, except that "filename*" uses the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.3"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[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. 1">[ISO-8859-1]</cite></a>). When both "filename" and "filename*" are present, a recipient <em class="bcp14">SHOULD</em> pick "filename*" and ignore "filename" - this will make it possible to send the same header value to clients that do not support
574         "filename*".
575      </p>
576      <p id="rfc.section.3.3.p.4">It is essential that user agents treat the specified filename as advisory only, thus be very careful in extracting the desired
577         information. In particular:
578      </p>
579      <ul>
580         <li>
581            <p>When the value contains path separator characters, all but the last segment <em class="bcp14">SHOULD</em> be ignored. This prevents unintentional overwriting of well-known file system location (such as "/etc/passwd").
582            </p>
583         </li>
584         <li>
585            <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
586               extension could introduce a privilege escalation when later on the file is opened locally (consider ".exe"). Thus, recipients
587               need to ensure that a file extension is used that is safe, optimally matching the media type of the received payload.
588            </p>
589         </li>
590         <li>
591            <p>Other aspects recipients need to be aware of are names that have a special meaning in the filesystem or in shell commands,
592               such as "." and "..", "~", "|", and also device names.
593            </p>
594         </li>
595      </ul>
596      <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="disposition.parameter.extensionsS" href="#disposition.parameter.extensionsS">Disposition Parameter: Extensions</a></h2>
597      <p id="rfc.section.3.4.p.1">To enable future extensions, unknown parameters <em class="bcp14">SHOULD</em> be ignored (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>).
598      </p>
599      <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a id="extensibility" href="#extensibility">Extensibility</a></h2>
600      <p id="rfc.section.3.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
601         using Content-Disposition, such as MIME and HTTP. Therefore, not all registered values may make sense in the context of HTTP.
602      </p>
603      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;Examples
604      </h1>
605      <div id="rfc.figure.u.4"></div>
606      <p>Direct UA to show "save as" dialog, with a filename of "foo.html":</p>  <pre class="text">Content-Disposition: Attachment; filename=foo.html
607</pre><div id="rfc.figure.u.5"></div>
608      <p>Direct UA to behave as if the Content-Disposition header field wasn't present, but to remember the filename "foo.html" for
609         a subsequent save operation:
610      </p>  <pre class="text">Content-Disposition: INLINE; FILENAME= "foo.html"
611</pre><div id="rfc.figure.u.6"></div>
612      <p>Direct UA to show "save as" dialog, with a filename of "an example":</p>  <pre class="text">Content-Disposition: Attachment; Filename*=UTF-8'<b>en</b>'an<b>%20</b>example
613</pre>  <p>Note that this example uses the extended encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.4"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a> to specify that the natural language of the filename is English, and also to encode the space character which is not allowed
614         in the token production.
615      </p>
616      <div id="rfc.figure.u.7"></div>
617      <p>Direct UA to show "save as" dialog, with a filename containing the Unicode character U+20AC (EURO SIGN):</p>  <pre class="text">Content-Disposition: attachment; filename*= UTF-8''<b>%e2%82%ac</b>%20rates
618</pre>  <p>Here, the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.5"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a> is also used to encode the non-ISO-8859-1 character.
619      </p>
620      <div id="rfc.figure.u.8"></div>
621      <p>Same as above, but adding the "filename" parameter for compatibility with user agents not implementing RFC 5987:</p>  <pre class="text">Content-Disposition: attachment; filename="EURO rates";
622                                 filename*=utf-8''<b>%e2%82%ac</b>%20rates
623</pre>  <p>Note: as of August 2010, many user agents unfortunately did not properly handle unexpected parameters, and some that implement
624         RFC 5987 did not pick the extended parameter when both were present.
625      </p>
626      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="i18n" href="#i18n">Internationalization Considerations</a></h1>
627      <p id="rfc.section.5.p.1">The "filename*" parameter (<a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;3.3</a>), using the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.6"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>, allows the server to transmit characters outside the ISO-8859-1 character set, and also to optionally specify the language
628         in use.
629      </p>
630      <p id="rfc.section.5.p.2">Future parameters might also require internationalization, in which case the same encoding can be used.</p>
631      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
632      <p id="rfc.section.6.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;3.3</a>.
633      </p>
634      <p id="rfc.section.6.p.2">Furthermore, implementers also 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.7"><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.7"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a> (see <a href="#RFC5987" id="rfc.xref.RFC5987.8"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>).
635      </p>
636      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="iana.considerations" href="#iana.considerations">IANA Considerations</a></h1>
637      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="registry" href="#registry">Registry for Disposition Values and Parameter</a></h2>
638      <p id="rfc.section.7.1.p.1">This specification does not introduce any changes to the registration procedures for disposition values and parameters that
639         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>.
640      </p>
641      <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
642      <p id="rfc.section.7.2.p.1">This document updates the definition of the Content-Disposition HTTP header field in the permanent HTTP header field registry
643         (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>).
644      </p>
645      <p id="rfc.section.7.2.p.2"> </p>
646      <dl>
647         <dt>Header field name:</dt>
648         <dd>Content-Disposition</dd>
649         <dt>Applicable protocol:</dt>
650         <dd>http</dd>
651         <dt>Status:</dt>
652         <dd>standard</dd>
653         <dt>Author/Change controller:</dt>
654         <dd>IETF</dd>
655         <dt>Specification document:</dt>
656         <dd>this specification (<a href="#header.field.definition" id="rfc.xref.header.field.definition.1" title="Header Field Definition">Section&nbsp;3</a>)
657         </dd>
658      </dl>
659      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;Acknowledgements
660      </h1>
661      <p id="rfc.section.8.p.1">Thanks to Rolf Eike Beer, Alfred Hoenes, and Roar Lauritzsen for their valuable feedback.</p>
662      <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References
663      </h1>
664      <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References
665      </h2>
666      <table>       
667         <tr>
668            <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td>
669            <td class="top">International Organization for Standardization, “Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1”, ISO/IEC&nbsp;8859-1:1998, 1998.</td>
670         </tr>
671         <tr>
672            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
673            <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.
674            </td>
675         </tr>
676         <tr>
677            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
678            <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.
679            </td>
680         </tr>
681         <tr>
682            <td class="reference"><b id="RFC5987">[RFC5987]</b></td>
683            <td class="top"><a href="" title="greenbytes GmbH">Reschke, J.</a>, “<a href="">Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers</a>”, RFC&nbsp;5987, August&nbsp;2010.
684            </td>
685         </tr>
686      </table>
687      <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
688      </h2>
689      <table>             
690         <tr>
691            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
692            <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.
693            </td>
694         </tr>
695         <tr>
696            <td class="reference"><b id="RFC2047">[RFC2047]</b></td>
697            <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.
698            </td>
699         </tr>
700         <tr>
701            <td class="reference"><b id="RFC2183">[RFC2183]</b></td>
702            <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</a>, “<a href="">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</a>”, RFC&nbsp;2183, August&nbsp;1997.
703            </td>
704         </tr>
705         <tr>
706            <td class="reference"><b id="RFC2231">[RFC2231]</b></td>
707            <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.
708            </td>
709         </tr>
710         <tr>
711            <td class="reference"><b id="RFC3629">[RFC3629]</b></td>
712            <td class="top"><a href="" title="Alis Technologies">Yergeau, F.</a>, “<a href="">UTF-8, a transformation format of ISO 10646</a>”, RFC&nbsp;3629, STD&nbsp;63, November&nbsp;2003.
713            </td>
714         </tr>
715         <tr>
716            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
717            <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.
718            </td>
719         </tr>
720         <tr>
721            <td class="reference"><b id="RFC3986">[RFC3986]</b></td>
722            <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>”, RFC&nbsp;3986, STD&nbsp;66, January&nbsp;2005.
723            </td>
724         </tr>
725      </table>
726      <div class="avoidbreak">
727         <h1 id="rfc.authors"><a href="#rfc.authors">Author's Address</a></h1>
728         <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>
729      </div>
730      <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>
731      <p id="rfc.section.A.p.1">Compared to <a href="">Section 19.5.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.8"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, the following normative changes reflecting actual implementations have been made:
732      </p>
733      <ul>
734         <li>According to RFC 2616, the disposition type "attachment" only applies to content of type "application/octet-stream". This
735            restriction has been removed, because user agents in practice do not check the content type, and it also discourages properly
736            declaring the media type.
737         </li>
738         <li>RFC 2616 only allows "quoted-string" for the filename parameter. This would be an exceptional parameter syntax, and also doesn't
739            reflect actual use.
740         </li>
741         <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.
742         </li>
743         <li>This specification requires support for the extended parameter encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.9"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>.
744         </li>
745      </ul>
746      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="" href="">Differences compared to RFC 2183</a></h1>
747      <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". These
748         do not appear to be implemented by any user agent, thus have been omitted from this specification.
749      </p>
750      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="alternatives" href="#alternatives">Alternative Approaches to Internationalization</a></h1>
751      <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. 1">[ISO-8859-1]</cite></a>) character encoding (see <a href="#RFC2616" id="rfc.xref.RFC2616.9"><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.
752      </p>
753      <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
754         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.10"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>).
755      </p>
756      <p id="rfc.section.C.p.3">For completeness, the sections below describe the various approaches that have been tried, and explains how they are inferior
757         to the RFC 5987 encoding used in this specification.
758      </p>
759      <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>
760      <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
761         - 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>:
762      </p>
763      <blockquote id="rfc.section.C.1.p.2" cite="">
764         <p>An 'encoded-word' MUST NOT appear within a 'quoted-string'.</p> 
765         <p>...</p> 
766         <p>An 'encoded-word' MUST NOT be used in parameter of a MIME Content-Type or Content-Disposition field, or in any structured
767            field body except within a 'comment' or 'phrase'.
768         </p>
769      </blockquote>
770      <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
771         confused by it.
772      </p>
773      <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>
774      <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 encoded using the UTF-8 (<a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a>) character encoding.
775      </p>
776      <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
777         to the user.
778      </p>
779      <p id="rfc.section.C.2.p.3">Furthermore, the first user agent to implement this did choose the encoding based on local settings; thus making it very hard
780         to use in multi-lingual environments.
781      </p>
782      <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>
783      <p id="rfc.section.C.3.p.1">Some user agents inspect the value (which defaults to ISO-8859-1) and switch to UTF-8 when it seems to be more likely to be
784         the correct interpretation.
785      </p>
786      <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>
787      <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a id="alternatives.implementations" href="#alternatives.implementations">Implementations</a></h2>
788      <p id="rfc.section.C.4.p.1">Unfortunately, as of August 2010, neither the encoding defined in RFCs 2231 and 5789, nor any of the alternate approaches
789         discussed above was implemented interoperably. Thus, this specification recommends the approach defined in RFC 5987, which
790         at least has the advantage of actually being specified properly.
791      </p>
792      <p id="rfc.section.C.4.p.2">The table below shows the implementation support for the various approaches: <span class="comment" id="impls">[<a href="#impls" class="smpl">impls</a>: Discuss: should we mention the implementation status of actual UAs in a RFC? Up to the IESG to decide...]</span>
793      </p>
794      <div id="rfc.table.u.1">
795         <table class="tt full left" cellpadding="3" cellspacing="0">
796            <thead>
797               <tr>
798                  <th>User Agent</th>
799                  <th>RFC 2231/5987</th>
800                  <th>RFC 2047</th>
801                  <th>Percent Encoding</th>
802                  <th>Encoding Sniffing</th>
803               </tr>
804            </thead>
805            <tbody>
806               <tr>
807                  <td class="left">Chrome</td>
808                  <td class="left">no</td>
809                  <td class="left">yes</td>
810                  <td class="left">yes</td>
811                  <td class="left">yes</td>
812               </tr>
813               <tr>
814                  <td class="left">Firefox</td>
815                  <td class="left">yes (*)</td>
816                  <td class="left">yes</td>
817                  <td class="left">no</td>
818                  <td class="left">yes</td>
819               </tr>
820               <tr>
821                  <td class="left">Internet Explorer</td>
822                  <td class="left">no</td>
823                  <td class="left">no</td>
824                  <td class="left">yes</td>
825                  <td class="left">no</td>
826               </tr>
827               <tr>
828                  <td class="left">Konqueror</td>
829                  <td class="left">yes</td>
830                  <td class="left">no</td>
831                  <td class="left">no</td>
832                  <td class="left">no</td>
833               </tr>
834               <tr>
835                  <td class="left">Opera</td>
836                  <td class="left">yes (*)</td>
837                  <td class="left">no</td>
838                  <td class="left">no</td>
839                  <td class="left">no</td>
840               </tr>
841               <tr>
842                  <td class="left">Safari</td>
843                  <td class="left">no</td>
844                  <td class="left">no</td>
845                  <td class="left">no</td>
846                  <td class="left">yes</td>
847               </tr>
848            </tbody>
849         </table>
850         <p>(*) Does not implement the fallback behavior to "filename" described in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;3.3</a>.
851         </p>
852      </div>
853      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
854      <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since draft-reschke-rfc2183-in-http-00
855      </h2>
856      <p id="rfc.section.D.1.p.1">Adjust terminology ("header" -&gt; "header field"). Update rfc2231-in-http reference.</p>
857      <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-reschke-rfc2183-in-http-01
858      </h2>
859      <p id="rfc.section.D.2.p.1">Update rfc2231-in-http reference. Actually define the "filename" parameter. Add internationalization considerations. Add examples
860         using the RFC 5987 encoding. Add overview over other approaches, plus a table reporting implementation status. Add and resolve
861         issue "nodep2183". Add issues "asciivsiso", "deplboth", "quoted", and "registry".
862      </p>
863      <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-reschke-rfc2183-in-http-02
864      </h2>
865      <p id="rfc.section.D.3.p.1">Add and close issue "docfallback". Close issues "asciivsiso", "deplboth", "quoted", and "registry".</p>
866      <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a>&nbsp;Since draft-reschke-rfc2183-in-http-03
867      </h2>
868      <p id="rfc.section.D.4.p.1">Updated to be a Working Draft of the IETF HTTPbis Working Group.</p>
869      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
870      <p class="noprint"><a href="#rfc.index.C">C</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.R">R</a>
871      </p>
872      <div class="print2col">
873         <ul class="ind">
874            <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">
875                  <li class="indline1">Content-Disposition header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.1"><b>3</b></a>, <a class="iref" href="#rfc.xref.header.field.definition.1">7.2</a></li>
876               </ul>
877            </li>
878            <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">
879                  <li class="indline1">Headers&nbsp;&nbsp;
880                     <ul class="ind">
881                        <li class="indline1">Content-Disposition&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.1"><b>3</b></a>, <a class="iref" href="#rfc.xref.header.field.definition.1">7.2</a></li>
882                     </ul>
883                  </li>
884               </ul>
885            </li>
886            <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">
887                  <li class="indline1"><em>ISO-8859-1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.ISO-8859-1.1">3.3</a>, <a class="iref" href="#ISO-8859-1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.ISO-8859-1.2">C</a></li>
888               </ul>
889            </li>
890            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
891                  <li class="indline1"><em>RFC2046</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2046.1">3.3</a>, <a class="iref" href="#RFC2046"><b>9.2</b></a></li>
892                  <li class="indline1"><em>RFC2047</em>&nbsp;&nbsp;<a class="iref" href="#RFC2047"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2047.1">C.1</a><ul class="ind">
893                        <li class="indline1"><em>Section 5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2047.1">C.1</a></li>
894                     </ul>
895                  </li>
896                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">2</a>, <a class="iref" href="#RFC2119"><b>9.1</b></a></li>
897                  <li class="indline1"><em>RFC2183</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2183.1">1</a>, <a class="iref" href="#rfc.xref.RFC2183.2">3.2</a>, <a class="iref" href="#rfc.xref.RFC2183.3">3.4</a>, <a class="iref" href="#rfc.xref.RFC2183.4">3.5</a>, <a class="iref" href="#rfc.xref.RFC2183.5">7.1</a>, <a class="iref" href="#RFC2183"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2183.6">A</a>, <a class="iref" href="#rfc.xref.RFC2183.7">B</a><ul class="ind">
898                        <li class="indline1"><em>Section 2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2183.7">B</a></li>
899                        <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2183.6">A</a></li>
900                        <li class="indline1"><em>Section 2.8</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2183.2">3.2</a>, <a class="iref" href="#rfc.xref.RFC2183.3">3.4</a></li>
901                        <li class="indline1"><em>Section 9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2183.4">3.5</a>, <a class="iref" href="#rfc.xref.RFC2183.5">7.1</a></li>
902                     </ul>
903                  </li>
904                  <li class="indline1"><em>RFC2231</em>&nbsp;&nbsp;<a class="iref" href="#RFC2231"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2231.1">C</a></li>
905                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#rfc.xref.RFC2616.3">2</a>, <a class="iref" href="#rfc.xref.RFC2616.4">3.1</a>, <a class="iref" href="#rfc.xref.RFC2616.5">3.1</a>, <a class="iref" href="#rfc.xref.RFC2616.6">3.1</a>, <a class="iref" href="#rfc.xref.RFC2616.7">6</a>, <a class="iref" href="#RFC2616"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC2616.8">A</a>, <a class="iref" href="#rfc.xref.RFC2616.9">C</a><ul class="ind">
906                        <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.3">2</a></li>
907                        <li class="indline1"><em>Section 2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.5">3.1</a>, <a class="iref" href="#rfc.xref.RFC2616.9">C</a></li>
908                        <li class="indline1"><em>Section 3.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.6">3.1</a></li>
909                        <li class="indline1"><em>Section 15.5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.2">1</a></li>
910                        <li class="indline1"><em>Section 15</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.7">6</a></li>
911                        <li class="indline1"><em>Section 19.5.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.8">A</a></li>
912                     </ul>
913                  </li>
914                  <li class="indline1"><em>RFC3629</em>&nbsp;&nbsp;<a class="iref" href="#RFC3629"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC3629.1">C.2</a></li>
915                  <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">7.2</a>, <a class="iref" href="#RFC3864"><b>9.2</b></a></li>
916                  <li class="indline1"><em>RFC3986</em>&nbsp;&nbsp;<a class="iref" href="#RFC3986"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC3986.1">C.2</a><ul class="ind">
917                        <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.1">C.2</a></li>
918                     </ul>
919                  </li>
920                  <li class="indline1"><em>RFC5987</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5987.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC5987.2">3.1</a>, <a class="iref" href="#rfc.xref.RFC5987.3">3.3</a>, <a class="iref" href="#rfc.xref.RFC5987.4">4</a>, <a class="iref" href="#rfc.xref.RFC5987.5">4</a>, <a class="iref" href="#rfc.xref.RFC5987.6">5</a>, <a class="iref" href="#rfc.xref.RFC5987.7">6</a>, <a class="iref" href="#rfc.xref.RFC5987.8">6</a>, <a class="iref" href="#RFC5987"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC5987.9">A</a>, <a class="iref" href="#rfc.xref.RFC5987.10">C</a><ul class="ind">
921                        <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5987.2">3.1</a></li>
922                     </ul>
923                  </li>
924               </ul>
925            </li>
926         </ul>
927      </div>
928   </body>
Note: See TracBrowser for help on using the repository browser.