source: draft-ietf-httpbis-content-disp/07/draft-ietf-httpbis-content-disp.html @ 2726

Last change on this file since 2726 was 2726, checked in by julian.reschke@…, 6 years ago

update to latest version of rfc2629.xslt, regen all HTML

  • Property svn:eol-style set to native
File size: 72.2 KB
Line 
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
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;
11}
12a.smpl {
13  color: black;
14}
15a:hover {
16  text-decoration: underline;
17}
18a:active {
19  text-decoration: underline;
20}
21address {
22  margin-top: 1em;
23  margin-left: 2em;
24  font-style: normal;
25}
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;
32}
33body {
34  color: black;
35  font-family: cambria, helvetica, arial, sans-serif;
36  font-size: 11pt;
37  margin-right: 2em;
38}
39cite {
40  font-style: normal;
41}
42div.note {
43  margin-left: 2em;
44}
45dl {
46  margin-left: 2em;
47}
48ul.empty {
49  list-style-type: none;
50}
51ul.empty li {
52  margin-top: .5em;
53}
54dl p {
55  margin-left: 0em;
56}
57dt {
58  margin-top: .5em;
59}
60h1 {
61  font-size: 130%;
62  line-height: 21pt;
63  page-break-after: avoid;
64}
65h1.np {
66  page-break-before: always;
67}
68h2 {
69  font-size: 120%;
70  line-height: 15pt;
71  page-break-after: avoid;
72}
73h3 {
74  font-size: 110%;
75  page-break-after: avoid;
76}
77h4, h5, h6 {
78  page-break-after: avoid;
79}
80h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
81  color: black;
82}
83img {
84  margin-left: 3em;
85}
86li {
87  margin-left: 2em;
88}
89ol {
90  margin-left: 2em;
91}
92ol.la {
93  list-style-type: lower-alpha;
94}
95ol.ua {
96  list-style-type: upper-alpha;
97}
98ol p {
99  margin-left: 0em;
100}
101p {
102  margin-left: 2em;
103}
104pre {
105  margin-left: 3em;
106  background-color: lightyellow;
107  padding: .25em;
108  page-break-inside: avoid;
109}
110pre.text2 {
111  border-style: dotted;
112  border-width: 1px;
113  background-color: #f0f0f0;
114  width: 69em;
115}
116pre.inline {
117  background-color: white;
118  padding: 0em;
119}
120pre.text {
121  border-style: dotted;
122  border-width: 1px;
123  background-color: #f8f8f8;
124  width: 69em;
125}
126pre.drawing {
127  border-style: solid;
128  border-width: 1px;
129  background-color: #f8f8f8;
130  padding: 2em;
131}
132table {
133  margin-left: 2em;
134}
135table.tt {
136  vertical-align: top;
137  border-color: gray;
138}
139table.tt th {
140  border-color: gray;
141}
142table.tt td {
143  border-color: gray;
144}
145table.all {
146  border-style: solid;
147  border-width: 2px;
148}
149table.full {
150  border-style: solid;
151  border-width: 2px;
152}
153table.tt td {
154  vertical-align: top;
155}
156table.all td {
157  border-style: solid;
158  border-width: 1px;
159}
160table.full td {
161  border-style: none solid;
162  border-width: 1px;
163}
164table.tt th {
165  vertical-align: top;
166}
167table.all th {
168  border-style: solid;
169  border-width: 1px;
170}
171table.full th {
172  border-style: solid;
173  border-width: 1px 1px 2px 1px;
174}
175table.headers th {
176  border-style: none none solid none;
177  border-width: 2px;
178}
179table.left {
180  margin-right: auto;
181}
182table.right {
183  margin-left: auto;
184}
185table.center {
186  margin-left: auto;
187  margin-right: auto;
188}
189caption {
190  caption-side: bottom;
191  font-weight: bold;
192  font-size: 10pt;
193  margin-top: .5em;
194}
195
196table.header {
197  border-spacing: 1px;
198  width: 95%;
199  font-size: 11pt;
200  color: white;
201}
202td.top {
203  vertical-align: top;
204}
205td.topnowrap {
206  vertical-align: top;
207  white-space: nowrap;
208}
209table.header td {
210  background-color: gray;
211  width: 50%;
212}
213table.header a {
214  color: white;
215}
216td.reference {
217  vertical-align: top;
218  white-space: nowrap;
219  padding-right: 1em;
220}
221thead {
222  display:table-header-group;
223}
224ul.toc, ul.toc ul {
225  list-style: none;
226  margin-left: 1.5em;
227  padding-left: 0em;
228}
229ul.toc li {
230  line-height: 150%;
231  font-weight: bold;
232  margin-left: 0em;
233}
234ul.toc li li {
235  line-height: normal;
236  font-weight: normal;
237  font-size: 10pt;
238  margin-left: 0em;
239}
240li.excluded {
241  font-size: 0pt;
242}
243ul p {
244  margin-left: 0em;
245}
246.title, .filename, h1, h2, h3, h4 {
247  font-family: candara, helvetica, arial, sans-serif;
248}
249samp, tt, code, pre {
250  font: consolas, monospace;
251}
252ul.ind, ul.ind ul {
253  list-style: none;
254  margin-left: 1.5em;
255  padding-left: 0em;
256  page-break-before: avoid;
257}
258ul.ind li {
259  font-weight: bold;
260  line-height: 200%;
261  margin-left: 0em;
262}
263ul.ind li li {
264  font-weight: normal;
265  line-height: 150%;
266  margin-left: 0em;
267}
268.avoidbreak {
269  page-break-inside: avoid;
270}
271.bcp14 {
272  font-style: normal;
273  text-transform: lowercase;
274  font-variant: small-caps;
275}
276blockquote > * .bcp14 {
277  font-style: italic;
278}
279.comment {
280  background-color: yellow;
281}
282.center {
283  text-align: center;
284}
285.error {
286  color: red;
287  font-style: italic;
288  font-weight: bold;
289}
290.figure {
291  font-weight: bold;
292  text-align: center;
293  font-size: 10pt;
294}
295.filename {
296  color: #333333;
297  font-size: 75%;
298  font-weight: bold;
299  line-height: 21pt;
300  text-align: center;
301}
302.fn {
303  font-weight: bold;
304}
305.left {
306  text-align: left;
307}
308.right {
309  text-align: right;
310}
311.title {
312  color: green;
313  font-size: 150%;
314  line-height: 18pt;
315  font-weight: bold;
316  text-align: center;
317  margin-top: 36pt;
318}
319.warning {
320  font-size: 130%;
321  background-color: yellow;
322}
323
324
325@media print {
326  .noprint {
327    display: none;
328  }
329
330  a {
331    color: black;
332    text-decoration: none;
333  }
334
335  table.header {
336    width: 90%;
337  }
338
339  td.header {
340    width: 50%;
341    color: black;
342    background-color: white;
343    vertical-align: top;
344    font-size: 110%;
345  }
346
347  ul.toc a:nth-child(2)::after {
348    content: leader('.') target-counter(attr(href), page);
349  }
350
351  ul.ind li li a {
352    content: target-counter(attr(href), page);
353  }
354
355  .print2col {
356    column-count: 2;
357    -moz-column-count: 2;
358    column-fill: auto;
359  }
360}
361
362@page {
363  @top-left {
364       content: "Internet-Draft";
365  }
366  @top-right {
367       content: "March 2011";
368  }
369  @top-center {
370       content: "Content-Disposition in HTTP";
371  }
372  @bottom-left {
373       content: "Reschke";
374  }
375  @bottom-center {
376       content: "Expires September 15, 2011";
377  }
378  @bottom-right {
379       content: "[Page " counter(page) "]";
380  }
381}
382
383@page:first {
384    @top-left {
385      content: normal;
386    }
387    @top-right {
388      content: normal;
389    }
390    @top-center {
391      content: normal;
392    }
393}
394</style><link rel="Contents" href="#rfc.toc">
395      <link rel="Author" href="#rfc.authors">
396      <link rel="Copyright" href="#rfc.copyrightnotice">
397      <link rel="Index" href="#rfc.index">
398      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
399      <link rel="Chapter" title="2 Notational Conventions" href="#rfc.section.2">
400      <link rel="Chapter" title="3 Conformance and Error Handling" href="#rfc.section.3">
401      <link rel="Chapter" title="4 Header Field Definition" href="#rfc.section.4">
402      <link rel="Chapter" title="5 Examples" href="#rfc.section.5">
403      <link rel="Chapter" title="6 Internationalization Considerations" href="#rfc.section.6">
404      <link rel="Chapter" title="7 Security Considerations" href="#rfc.section.7">
405      <link rel="Chapter" title="8 IANA Considerations" href="#rfc.section.8">
406      <link rel="Chapter" title="9 Acknowledgements" href="#rfc.section.9">
407      <link rel="Chapter" href="#rfc.section.10" title="10 References">
408      <link rel="Appendix" title="A Changes from the RFC 2616 Definition" href="#rfc.section.A">
409      <link rel="Appendix" title="B Differences compared to RFC 2183" href="#rfc.section.B">
410      <link rel="Appendix" title="C Alternative Approaches to Internationalization" href="#rfc.section.C">
411      <link rel="Appendix" title="D Advice on Generating Content-Disposition Header Fields" href="#rfc.section.D">
412      <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E">
413      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
414      <link rel="schema.dct" href="http://purl.org/dc/terms/">
415      <meta name="dct.creator" content="Reschke, J. F.">
416      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-07">
417      <meta name="dct.issued" scheme="ISO8601" content="2011-03-14">
418      <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.">
419      <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.">
420   </head>
421   <body>
422      <table class="header">
423         <tbody>
424            <tr>
425               <td class="left">HTTPbis Working Group</td>
426               <td class="right">J. Reschke</td>
427            </tr>
428            <tr>
429               <td class="left">Internet-Draft</td>
430               <td class="right">greenbytes</td>
431            </tr>
432            <tr>
433               <td class="left">Updates: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
434               </td>
435               <td class="right">March 14, 2011</td>
436            </tr>
437            <tr>
438               <td class="left">Intended status: Standards Track</td>
439               <td class="right"></td>
440            </tr>
441            <tr>
442               <td class="left">Expires: September 15, 2011</td>
443               <td class="right"></td>
444            </tr>
445         </tbody>
446      </table>
447      <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-07</span></p>
448      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
449      <p>RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard.
450         This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization
451         aspects.
452      </p>
453      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor before publication)</a></h1>
454      <p>This specification is expected to replace the definition of Content-Disposition in the HTTP/1.1 specification, as currently
455         revised by the IETF HTTPbis working group. See also &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/123">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/123</a>&gt;.
456      </p>
457      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
458         list is at &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/query?component=content-disp">http://trac.tools.ietf.org/wg/httpbis/trac/query?component=content-disp</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
459      </p>
460      <p>The changes in this draft are summarized in <a href="#changes.since.06" title="Since draft-ietf-httpbis-content-disp-06">Appendix&nbsp;E.11</a>.
461      </p>
462      <div id="rfc.status">
463         <h1><a href="#rfc.status">Status of This Memo</a></h1>
464         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
465         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
466            working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
467         </p>
468         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
469            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
470            in progress”.
471         </p>
472         <p>This Internet-Draft will expire on September 15, 2011.</p>
473      </div>
474      <div id="rfc.copyrightnotice">
475         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
476         <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
477         <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
478            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
479            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
480            BSD License.
481         </p>
482      </div>
483      <hr class="noprint">
484      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
485      <ul class="toc">
486         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a></li>
487         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#notational.conventions">Notational Conventions</a></li>
488         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#conformance.and.error.handling">Conformance and Error Handling</a></li>
489         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.definition">Header Field Definition</a><ul>
490               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.1">Grammar</a></li>
491               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#disposition.type">Disposition Type</a></li>
492               <li><a href="#rfc.section.4.3">4.3</a>&nbsp;&nbsp;&nbsp;<a href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></li>
493               <li><a href="#rfc.section.4.4">4.4</a>&nbsp;&nbsp;&nbsp;<a href="#disposition.parameter.extensions">Disposition Parameter: Extensions</a></li>
494               <li><a href="#rfc.section.4.5">4.5</a>&nbsp;&nbsp;&nbsp;<a href="#extensibility">Extensibility</a></li>
495            </ul>
496         </li>
497         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#examples">Examples</a></li>
498         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#i18n">Internationalization Considerations</a></li>
499         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
500         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#iana.considerations">IANA Considerations</a><ul>
501               <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#registry">Registry for Disposition Values and Parameter</a></li>
502               <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
503            </ul>
504         </li>
505         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9">Acknowledgements</a></li>
506         <li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
507               <li><a href="#rfc.section.10.1">10.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
508               <li><a href="#rfc.section.10.2">10.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
509            </ul>
510         </li>
511         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc2616">Changes from the RFC 2616 Definition</a></li>
512         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#diffs.compared.to.rfc2183">Differences compared to RFC 2183</a></li>
513         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#alternatives">Alternative Approaches to Internationalization</a><ul>
514               <li><a href="#rfc.section.C.1">C.1</a>&nbsp;&nbsp;&nbsp;<a href="#alternatives.rfc2047">RFC 2047 Encoding</a></li>
515               <li><a href="#rfc.section.C.2">C.2</a>&nbsp;&nbsp;&nbsp;<a href="#alternatives.percent">Percent Encoding</a></li>
516               <li><a href="#rfc.section.C.3">C.3</a>&nbsp;&nbsp;&nbsp;<a href="#alternatives.sniff">Encoding Sniffing</a></li>
517               <li><a href="#rfc.section.C.4">C.4</a>&nbsp;&nbsp;&nbsp;<a href="#alternatives.implementations">Implementations (to be removed by RFC Editor before publication)</a></li>
518            </ul>
519         </li>
520         <li><a href="#rfc.section.D">D.</a>&nbsp;&nbsp;&nbsp;<a href="#advice.generating">Advice on Generating Content-Disposition Header Fields</a></li>
521         <li><a href="#rfc.section.E">E.</a>&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
522               <li><a href="#rfc.section.E.1">E.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.1">Since draft-reschke-rfc2183-in-http-00</a></li>
523               <li><a href="#rfc.section.E.2">E.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.2">Since draft-reschke-rfc2183-in-http-01</a></li>
524               <li><a href="#rfc.section.E.3">E.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.3">Since draft-reschke-rfc2183-in-http-02</a></li>
525               <li><a href="#rfc.section.E.4">E.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.4">Since draft-reschke-rfc2183-in-http-03</a></li>
526               <li><a href="#rfc.section.E.5">E.5</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.00">Since draft-ietf-httpbis-content-disp-00</a></li>
527               <li><a href="#rfc.section.E.6">E.6</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.01">Since draft-ietf-httpbis-content-disp-01</a></li>
528               <li><a href="#rfc.section.E.7">E.7</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-content-disp-02</a></li>
529               <li><a href="#rfc.section.E.8">E.8</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-content-disp-03</a></li>
530               <li><a href="#rfc.section.E.9">E.9</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-content-disp-04</a></li>
531               <li><a href="#rfc.section.E.10">E.10</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-content-disp-05</a></li>
532               <li><a href="#rfc.section.E.11">E.11</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-content-disp-06</a></li>
533            </ul>
534         </li>
535         <li><a href="#rfc.index">Index</a></li>
536         <li><a href="#rfc.authors">Author's Address</a></li>
537      </ul>
538      <div id="introduction">
539         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
540         <p id="rfc.section.1.p.1">RFC 2616 defines the Content-Disposition response header field in <a href="https://tools.ietf.org/html/rfc2616#section-19.5.1">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="https://tools.ietf.org/html/rfc2616#section-15.5" id="rfc.xref.RFC2616.2">Section 15.5</a>):
541         </p>
542         <blockquote id="rfc.section.1.p.2" cite="http://tools.ietf.org/html/rfc2616#section-15.5">
543            <p>Content-Disposition is not part of the HTTP standard, but since it is widely implemented, we are documenting its use and risks
544               for implementers.
545            </p>
546         </blockquote>
547         <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
548            testing with existing User Agents, it fully defines a profile of the features defined in the Multipurpose Internet Mail Extensions
549            (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.
550         </p>
551         <div class="note" id="rfc.section.1.p.4">
552            <p><b>Note:</b> this document does not apply to Content-Disposition header fields appearing in payload bodies transmitted over HTTP, such
553               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>).
554            </p>
555         </div>
556      </div>
557      <div id="notational.conventions">
558         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#notational.conventions">Notational Conventions</a></h1>
559         <p id="rfc.section.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
560            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>.
561         </p>
562         <p id="rfc.section.2.p.2">This specification uses the augmented BNF notation defined in <a href="https://tools.ietf.org/html/rfc2616#section-2.1">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).
563         </p>
564      </div>
565      <div id="conformance.and.error.handling">
566         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#conformance.and.error.handling">Conformance and Error Handling</a></h1>
567         <p id="rfc.section.3.p.1">This specification defines conformance criteria for both senders (usually, HTTP origin servers) and recipients (usually, HTTP
568            user agents) of the Content-Disposition header field. An implementation is considered conformant if it complies with all of
569            the requirements associated with its role.
570         </p>
571         <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,
572            but it does not define special handling of these invalid field-values.
573         </p>
574         <p id="rfc.section.3.p.3">Senders <em class="bcp14">MUST NOT</em> generate Content-Disposition header fields that are invalid.
575         </p>
576         <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 behaviour (e.g., the implementation is a validator). As such,
577            the default handling of invalid fields is to ignore them.
578         </p>
579      </div>
580      <div id="header.field.definition">
581         <div id="rfc.iref.h.1"></div>
582         <div id="rfc.iref.c.1"></div>
583         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#header.field.definition">Header Field Definition</a></h1>
584         <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,
585            and also can be used to attach additional metadata, such as the filename to use when saving the response payload locally.
586         </p>
587         <div>
588            <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;Grammar
589            </h2>
590            <div id="rfc.figure.u.1"></div><pre class="inline">  content-disposition = "Content-Disposition" ":"
591                         disposition-type *( ";" disposition-parm )
592
593  disposition-type    = "inline" | "attachment" | disp-ext-type
594                      ; case-insensitive
595  disp-ext-type       = token
596
597  disposition-parm    = filename-parm | disp-ext-parm
598
599  filename-parm       = "filename" "=" value
600                      | "filename*" "=" ext-value
601 
602  disp-ext-parm       = token "=" value
603                      | ext-token "=" ext-value
604  ext-token           = &lt;the characters in token, followed by "*"&gt;
605</pre><div id="rfc.figure.u.2"></div>
606            <p>Defined in <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>:
607            </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="https://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>&gt;
608  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="https://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>&gt;
609  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="https://tools.ietf.org/html/rfc2616#section-3.6">Section 3.6</a>&gt;
610                ; token | quoted-string
611             
612</pre><div id="rfc.figure.u.3"></div>
613            <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>:
614            </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="https://tools.ietf.org/html/rfc5987#section-3.2">Section 3.2</a>&gt;
615</pre><p id="rfc.section.4.1.p.4">Header field values with multiple instances of the same parameter name are invalid.</p>
616            <p id="rfc.section.4.1.p.5">Note that due to the rules for implied linear whitespace (<a href="https://tools.ietf.org/html/rfc2616#section-2.1">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.
617            </p>
618            <p id="rfc.section.4.1.p.6">Furthermore note that the format used for ext-value allows specifying a natural language; this is of limited use for filenames
619               and is likely to be ignored by recipients.
620            </p>
621         </div>
622         <div id="disposition.type">
623            <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#disposition.type">Disposition Type</a></h2>
624            <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
625               to save the response locally, rather than process it normally (as per its media type).
626            </p>
627            <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
628               type "inline" is only useful when it is augmented with additional parameters, such as the filename (see below).
629            </p>
630            <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="https://tools.ietf.org/html/rfc2183#section-2.8">Section 2.8</a>).
631            </p>
632         </div>
633         <div id="disposition.parameter.filename">
634            <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></h2>
635            <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
636               for storing the message payload.
637            </p>
638            <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
639               "attachment" disposition type), or later on (for instance, when the user decides to save the contents of the current page
640               being displayed).
641            </p>
642            <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. 1">[ISO-8859-1]</cite></a>).
643            </p>
644            <p id="rfc.section.4.3.p.4">Many user agent implementations predating this specification do not understand the "filename*" parameter. Therefore, when
645               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
646               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).
647            </p>
648            <p id="rfc.section.4.3.p.5">It is essential that recipients treat the specified filename as advisory only, thus be very careful in extracting the desired
649               information. In particular:
650            </p>
651            <ul>
652               <li>
653                  <p>When the value contains path separator characters ("\" or "/"), recipients <em class="bcp14">SHOULD</em> ignore all but the last path segment. This prevents unintentional overwriting of well-known file system locations (such as
654                     "/etc/passwd").
655                  </p>
656               </li>
657               <li>
658                  <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
659                     extension could introduce a privilege escalation when the saved file is later opened (consider ".exe"). Thus, recipients <em class="bcp14">SHOULD</em> ensure that a file extension is used that is safe, optimally matching the media type of the received payload.
660                  </p>
661               </li>
662               <li>
663                  <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
664                     characters and leading and trailing whitespace.
665                  </p>
666               </li>
667               <li>
668                  <p>Other aspects recipients need to be aware of are names that have a special meaning in the file system or in shell commands,
669                     such as "." and "..", "~", "|", and also device names. Recipients <em class="bcp14">SHOULD</em> ignore or substitute names like these.
670                  </p>
671               </li>
672            </ul>
673            <div class="note" id="rfc.section.4.3.p.6">
674               <p><b>Note:</b> Many user agents do not properly handle the escape character "\" when using the quoted-string form. Furthermore, some user
675                  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.
676               </p>
677            </div>
678         </div>
679         <div id="disposition.parameter.extensions">
680            <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a href="#disposition.parameter.extensions">Disposition Parameter: Extensions</a></h2>
681            <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="https://tools.ietf.org/html/rfc2183#section-2.8">Section 2.8</a>).
682            </p>
683         </div>
684         <div id="extensibility">
685            <h2 id="rfc.section.4.5"><a href="#rfc.section.4.5">4.5</a>&nbsp;<a href="#extensibility">Extensibility</a></h2>
686            <p id="rfc.section.4.5.p.1">Note that <a href="https://tools.ietf.org/html/rfc2183#section-9">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
687               using Content-Disposition, such as MIME and HTTP. Therefore, not all registered values may make sense in the context of HTTP.
688            </p>
689         </div>
690      </div>
691      <div id="examples">
692         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#examples">Examples</a></h1>
693         <div id="rfc.figure.u.4"></div>
694         <p>Direct UA to show "save as" dialog, with a filename of "example.html":</p><pre class="text">Content-Disposition: Attachment; filename=example.html
695</pre><div id="rfc.figure.u.5"></div>
696         <p>Direct UA to behave as if the Content-Disposition header field wasn't present, but to remember the filename "an example.html"
697            for a subsequent save operation:
698         </p><pre class="text">Content-Disposition: INLINE; FILENAME= "an example.html"
699</pre><p>Note: this uses the quoted-string form so that the space character can be included.</p>
700         <div id="rfc.figure.u.6"></div>
701         <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;
702                     filename*= UTF-8''<b>%e2%82%ac</b>%20rates
703</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.
704         </p>
705         <div id="rfc.figure.u.7"></div>
706         <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;
707                     filename="EURO rates";
708                     filename*=utf-8''<b>%e2%82%ac</b>%20rates
709</pre><p>Note: those user agents that do not support the RFC 5987 encoding ignore "filename*" when it occurs after "filename".</p>
710      </div>
711      <div id="i18n">
712         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#i18n">Internationalization Considerations</a></h1>
713         <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
714            in use.
715         </p>
716         <p id="rfc.section.6.p.2">Future parameters might also require internationalization, in which case the same encoding can be used.</p>
717      </div>
718      <div id="security.considerations">
719         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
720         <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>.
721         </p>
722         <p id="rfc.section.7.p.2">Furthermore, implementers also ought to be aware of the Security Considerations applying to HTTP (see <a href="https://tools.ietf.org/html/rfc2616#section-15">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="https://tools.ietf.org/html/rfc5987#section-5" id="rfc.xref.RFC5987.7">Section 5</a>).
723         </p>
724      </div>
725      <div id="iana.considerations">
726         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#iana.considerations">IANA Considerations</a></h1>
727         <div id="registry">
728            <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a href="#registry">Registry for Disposition Values and Parameter</a></h2>
729            <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
730               are defined in <a href="https://tools.ietf.org/html/rfc2183#section-9">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>.
731            </p>
732         </div>
733         <div id="header.field.registration">
734            <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
735            <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
736               (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>).
737            </p>
738            <p id="rfc.section.8.2.p.2"></p>
739            <dl>
740               <dt>Header field name:</dt>
741               <dd>Content-Disposition</dd>
742               <dt>Applicable protocol:</dt>
743               <dd>http</dd>
744               <dt>Status:</dt>
745               <dd>standard</dd>
746               <dt>Author/Change controller:</dt>
747               <dd>IETF</dd>
748               <dt>Specification document:</dt>
749               <dd>this specification (<a href="#header.field.definition" id="rfc.xref.header.field.definition.1" title="Header Field Definition">Section&nbsp;4</a>)
750               </dd>
751            </dl>
752         </div>
753      </div>
754      <div>
755         <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;Acknowledgements
756         </h1>
757         <p id="rfc.section.9.p.1">Thanks to Adam Barth, Rolf Eike Beer, Bjoern Hoehrmann, Alfred Hoenes, Roar Lauritzsen, Henrik Nordstrom, and Mark Nottingham
758            for their valuable feedback.
759         </p>
760      </div>
761      <h1 id="rfc.references"><a id="rfc.section.10" href="#rfc.section.10">10.</a> References
762      </h1>
763      <h2 id="rfc.references.1"><a href="#rfc.section.10.1" id="rfc.section.10.1">10.1</a> Normative References
764      </h2>
765      <table>
766         <tr>
767            <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td>
768            <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>
769         </tr>
770         <tr>
771            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
772            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
773            </td>
774         </tr>
775         <tr>
776            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
777            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
778            </td>
779         </tr>
780         <tr>
781            <td class="reference"><b id="RFC5987">[RFC5987]</b></td>
782            <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="https://tools.ietf.org/html/rfc5987">Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters</a>”, RFC&nbsp;5987, August&nbsp;2010.
783            </td>
784         </tr>
785      </table>
786      <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References
787      </h2>
788      <table>
789         <tr>
790            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
791            <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="https://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC&nbsp;2046, November&nbsp;1996.
792            </td>
793         </tr>
794         <tr>
795            <td class="reference"><b id="RFC2047">[RFC2047]</b></td>
796            <td class="top"><a href="mailto:moore@cs.utk.edu" title="University of Tennessee">Moore, K.</a>, “<a href="https://tools.ietf.org/html/rfc2047">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</a>”, RFC&nbsp;2047, November&nbsp;1996.
797            </td>
798         </tr>
799         <tr>
800            <td class="reference"><b id="RFC2183">[RFC2183]</b></td>
801            <td class="top"><a href="mailto:rens@century.com" title="New Century Systems">Troost, R.</a>, <a href="mailto:sdorner@qualcomm.com" title="QUALCOMM Incorporated">Dorner, S.</a>, and <a href="mailto:moore@cs.utk.edu" title="Department of Computer Science">K. Moore</a>, “<a href="https://tools.ietf.org/html/rfc2183">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</a>”, RFC&nbsp;2183, August&nbsp;1997.
802            </td>
803         </tr>
804         <tr>
805            <td class="reference"><b id="RFC2231">[RFC2231]</b></td>
806            <td class="top"><a href="mailto:ned.freed@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:moore@cs.utk.edu" title="University of Tennessee">K. Moore</a>, “<a href="https://tools.ietf.org/html/rfc2231">MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations</a>”, RFC&nbsp;2231, November&nbsp;1997.
807            </td>
808         </tr>
809         <tr>
810            <td class="reference"><b id="RFC2388">[RFC2388]</b></td>
811            <td class="top"><a href="mailto:masinter@parc.xerox.com" title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="https://tools.ietf.org/html/rfc2388">Returning Values from Forms: multipart/form-data</a>”, RFC&nbsp;2388, August&nbsp;1998.
812            </td>
813         </tr>
814         <tr>
815            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
816            <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
817            </td>
818         </tr>
819         <tr>
820            <td class="reference"><b id="RFC3986">[RFC3986]</b></td>
821            <td class="top"><a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R.</a>, and <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">L. Masinter</a>, “<a href="https://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, STD&nbsp;66, RFC&nbsp;3986, January&nbsp;2005.
822            </td>
823         </tr>
824      </table>
825      <div id="changes.from.rfc2616">
826         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#changes.from.rfc2616">Changes from the RFC 2616 Definition</a></h1>
827         <p id="rfc.section.A.p.1">Compared to <a href="https://tools.ietf.org/html/rfc2616#section-19.5.1">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:
828         </p>
829         <ul>
830            <li>According to RFC 2616, the disposition type "attachment" only applies to content of type "application/octet-stream". This
831               restriction has been removed, because recipients in practice do not check the content type, and it also discourages properly
832               declaring the media type.
833            </li>
834            <li>RFC 2616 only allows "quoted-string" for the filename parameter. This would be an exceptional parameter syntax, and also doesn't
835               reflect actual use.
836            </li>
837            <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="https://tools.ietf.org/html/rfc2183#section-2.1">Section 2.1</a>) has been re-added with a suggestion for its processing.
838            </li>
839            <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>.
840            </li>
841         </ul>
842      </div>
843      <div id="diffs.compared.to.rfc2183">
844         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#diffs.compared.to.rfc2183">Differences compared to RFC 2183</a></h1>
845         <p id="rfc.section.B.p.1"><a href="https://tools.ietf.org/html/rfc2183#section-2">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
846            majority of user agents does not implement these, thus they have been omitted from this specification.
847         </p>
848      </div>
849      <div id="alternatives">
850         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#alternatives">Alternative Approaches to Internationalization</a></h1>
851         <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.11"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="https://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>). For the "filename" parameter, this of course is an unacceptable restriction.
852         </p>
853         <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
854            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>).
855         </p>
856         <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
857            to the RFC 5987 encoding used in this specification.
858         </p>
859         <div id="alternatives.rfc2047">
860            <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;<a href="#alternatives.rfc2047">RFC 2047 Encoding</a></h2>
861            <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
862               - see <a href="https://tools.ietf.org/html/rfc2047#section-5">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>:
863            </p>
864            <blockquote id="rfc.section.C.1.p.2" cite="http://tools.ietf.org/html/rfc2047#section-5">
865               <p>An 'encoded-word' MUST NOT appear within a 'quoted-string'.</p>
866               <p>...</p>
867               <p>An 'encoded-word' MUST NOT be used in parameter of a MIME Content-Type or Content-Disposition field, or in any structured
868                  field body except within a 'comment' or 'phrase'.
869               </p>
870            </blockquote>
871            <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
872               confused by it.
873            </p>
874         </div>
875         <div id="alternatives.percent">
876            <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;<a href="#alternatives.percent">Percent Encoding</a></h2>
877            <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="https://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>) sequences of characters. The character encoding being used for decoding depends on various factors, including the encoding
878               of the referring page, the user agent's locale, its configuration, and also the actual value of the parameter.
879            </p>
880            <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
881               to the user. For those user agents that do implement this it is difficult to predict what character encoding they actually
882               expect.
883            </p>
884         </div>
885         <div id="alternatives.sniff">
886            <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;<a href="#alternatives.sniff">Encoding Sniffing</a></h2>
887            <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
888               to be more likely to be the correct interpretation.
889            </p>
890            <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>
891         </div>
892         <div id="alternatives.implementations">
893            <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a href="#alternatives.implementations">Implementations (to be removed by RFC Editor before publication)</a></h2>
894            <p id="rfc.section.C.4.p.1">Unfortunately, as of March 2011, neither the encoding defined in RFCs 2231 and 5987, nor any of the alternate approaches discussed
895               above was implemented interoperably. Thus, this specification recommends the approach defined in RFC 5987, which at least
896               has the advantage of actually being specified properly.
897            </p>
898            <p id="rfc.section.C.4.p.2">The table below shows the implementation support for the various approaches:</p>
899            <div id="rfc.table.u.1">
900               <table class="tt full left" cellpadding="3" cellspacing="0">
901                  <thead>
902                     <tr>
903                        <th>User Agent</th>
904                        <th>RFC 2231/5987</th>
905                        <th>RFC 2047</th>
906                        <th>Percent Encoding</th>
907                        <th>Encoding Sniffing</th>
908                     </tr>
909                  </thead>
910                  <tbody>
911                     <tr>
912                        <td class="left">Chrome</td>
913                        <td class="left">yes</td>
914                        <td class="left">yes</td>
915                        <td class="left">yes</td>
916                        <td class="left">yes</td>
917                     </tr>
918                     <tr>
919                        <td class="left">Firefox</td>
920                        <td class="left">yes (*)</td>
921                        <td class="left">yes</td>
922                        <td class="left">no</td>
923                        <td class="left">yes</td>
924                     </tr>
925                     <tr>
926                        <td class="left">Internet Explorer</td>
927                        <td class="left">yes (**)</td>
928                        <td class="left">no</td>
929                        <td class="left">yes</td>
930                        <td class="left">no</td>
931                     </tr>
932                     <tr>
933                        <td class="left">Konqueror</td>
934                        <td class="left">yes</td>
935                        <td class="left">no</td>
936                        <td class="left">no</td>
937                        <td class="left">no</td>
938                     </tr>
939                     <tr>
940                        <td class="left">Opera</td>
941                        <td class="left">yes</td>
942                        <td class="left">no</td>
943                        <td class="left">no</td>
944                        <td class="left">no</td>
945                     </tr>
946                     <tr>
947                        <td class="left">Safari</td>
948                        <td class="left">no</td>
949                        <td class="left">no</td>
950                        <td class="left">no</td>
951                        <td class="left">yes</td>
952                     </tr>
953                  </tbody>
954               </table>
955            </div>
956            <p id="rfc.section.C.4.p.3">(*) Does not implement the fallback behavior to "filename" described in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;4.3</a>; a fix is planned for Firefox 5.
957            </p>
958            <p id="rfc.section.C.4.p.4">(**) Starting with IE9RC, but only implements UTF-8.</p>
959         </div>
960      </div>
961      <div id="advice.generating">
962         <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a href="#advice.generating">Advice on Generating Content-Disposition Header Fields</a></h1>
963         <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
964            to:
965         </p>
966         <p id="rfc.section.D.p.2"></p>
967         <ul>
968            <li>Include a "filename" parameter when US-ASCII is sufficiently expressive.</li>
969            <li>Use the 'token' form of the filename parameter only when it does not contain disallowed characters (e.g., spaces); in such
970               cases, the quoted-string form should be used.
971            </li>
972            <li>Avoid including the percent character followed by two hexadecimal characters (e.g., %A9) in the filename parameter, since
973               some existing implementations consider it to be an escape character, while others will pass it through unchanged.
974            </li>
975            <li>Avoid including the "\" character in the quoted-string form of the filename parameter, as escaping is not implemented by some
976               user agents, and can be considered as an illegal path character.
977            </li>
978            <li>Avoid using non-ASCII characters in the filename parameter. Although most existing implementations will decode them as ISO-8859-1,
979               some will apply heuristics to detect UTF-8, and thus might fail on certain names.
980            </li>
981            <li>Include a "filename*" parameter where the desired filename cannot be expressed faithfully using the "filename" form. Note
982               that legacy user agents will not process this, and will fall back to using the "filename" parameter's content.
983            </li>
984            <li>When a "filename*" parameter is sent, to also generate a "filename" parameter as a fallback for user agents that do not support
985               the "filename*" form, if possible. This can be done by substituting characters with US-ASCII sequences (e.g., Unicode character
986               point U+00E4 (LATIN SMALL LETTER A WITH DIARESIS) by "ae"). Note that this may not be possible in some locales.
987            </li>
988            <li>When a "filename" parameter is included as a fallback (as per above), "filename" should occur first, due to parsing problems
989               in some existing implementations. <span class="comment" id="fallbackbug">[<a href="#fallbackbug" class="smpl">fallbackbug</a>: Firefox is known to pick the wrong parameter; a bug fix is scheduled for Firefox 5. --jre]</span>
990            </li>
991            <li>Use UTF-8 as the encoding of the "filename*" parameter, when present, because at least one existing implementation only implements
992               that encoding.
993            </li>
994         </ul>
995         <p id="rfc.section.D.p.3">Note that this advice is based upon UA behaviour at the time of writing, and might be superseded. &lt;<a href="http://purl.org/NET/http/content-disposition-tests">http://purl.org/NET/http/content-disposition-tests</a>&gt; provides an overview of current levels of support in various implementations.
996         </p>
997      </div>
998      <div id="change.log">
999         <h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
1000         <p id="rfc.section.E.p.1">Note: the issues names in the change log entries for draft-reschke-rfc2183-in-http refer to &lt;<a href="http://greenbytes.de/tech/webdav/draft-reschke-rfc2183-in-http-issues.html">http://greenbytes.de/tech/webdav/draft-reschke-rfc2183-in-http-issues.html</a>&gt;.
1001         </p>
1002         <div>
1003            <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;Since draft-reschke-rfc2183-in-http-00
1004            </h2>
1005            <p id="rfc.section.E.1.p.1">Adjust terminology ("header" -&gt; "header field"). Update rfc2231-in-http reference.</p>
1006         </div>
1007         <div>
1008            <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;Since draft-reschke-rfc2183-in-http-01
1009            </h2>
1010            <p id="rfc.section.E.2.p.1">Update rfc2231-in-http reference. Actually define the "filename" parameter. Add internationalization considerations. Add examples
1011               using the RFC 5987 encoding. Add overview over other approaches, plus a table reporting implementation status. Add and resolve
1012               issue "nodep2183". Add issues "asciivsiso", "deplboth", "quoted", and "registry".
1013            </p>
1014         </div>
1015         <div>
1016            <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a>&nbsp;Since draft-reschke-rfc2183-in-http-02
1017            </h2>
1018            <p id="rfc.section.E.3.p.1">Add and close issue "docfallback". Close issues "asciivsiso", "deplboth", "quoted", and "registry".</p>
1019         </div>
1020         <div>
1021            <h2 id="rfc.section.E.4"><a href="#rfc.section.E.4">E.4</a>&nbsp;Since draft-reschke-rfc2183-in-http-03
1022            </h2>
1023            <p id="rfc.section.E.4.p.1">Updated to be a Working Draft of the IETF HTTPbis Working Group.</p>
1024         </div>
1025         <div id="changes.since.00">
1026            <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;<a href="#changes.since.00">Since draft-ietf-httpbis-content-disp-00</a></h2>
1027            <p id="rfc.section.E.5.p.1">Closed issues: </p>
1028            <ul>
1029               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/242">http://tools.ietf.org/wg/httpbis/trac/ticket/242</a>&gt;: "handling of unknown disposition types"
1030               </li>
1031            </ul>
1032            <p id="rfc.section.E.5.p.2">Slightly updated the notes about the proposed fallback behavior.</p>
1033         </div>
1034         <div id="changes.since.01">
1035            <h2 id="rfc.section.E.6"><a href="#rfc.section.E.6">E.6</a>&nbsp;<a href="#changes.since.01">Since draft-ietf-httpbis-content-disp-01</a></h2>
1036            <p id="rfc.section.E.6.p.1">Various editorial improvements.</p>
1037         </div>
1038         <div id="changes.since.02">
1039            <h2 id="rfc.section.E.7"><a href="#rfc.section.E.7">E.7</a>&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-content-disp-02</a></h2>
1040            <p id="rfc.section.E.7.p.1">Closed issues: </p>
1041            <ul>
1042               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/244">http://tools.ietf.org/wg/httpbis/trac/ticket/244</a>&gt;: "state that repeating parameters are invalid"
1043               </li>
1044               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/245">http://tools.ietf.org/wg/httpbis/trac/ticket/245</a>&gt;: "warn about %xx in filenames being misinterpreted"
1045               </li>
1046               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/246">http://tools.ietf.org/wg/httpbis/trac/ticket/246</a>&gt;: "mention control chars when talking about postprecessing the filename parameter"
1047               </li>
1048            </ul>
1049            <p id="rfc.section.E.7.p.2">Update <a href="#alternatives.implementations" title="Implementations (to be removed by RFC Editor before publication)">Appendix&nbsp;C.4</a>; Opera 10.63 RC implements the recommended fallback behavior.
1050            </p>
1051         </div>
1052         <div id="changes.since.03">
1053            <h2 id="rfc.section.E.8"><a href="#rfc.section.E.8">E.8</a>&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-content-disp-03</a></h2>
1054            <p id="rfc.section.E.8.p.1">Closed issues: </p>
1055            <ul>
1056               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/252">http://tools.ietf.org/wg/httpbis/trac/ticket/252</a>&gt;: "'modification-date' *is* implemented in Konq 4.5"
1057               </li>
1058               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/253">http://tools.ietf.org/wg/httpbis/trac/ticket/253</a>&gt;: "clarify what LWS means for the Content-Disp grammar"
1059               </li>
1060               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/258">http://tools.ietf.org/wg/httpbis/trac/ticket/258</a>&gt;: "Avoid passive voice in message requirements"
1061               </li>
1062               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/263">http://tools.ietf.org/wg/httpbis/trac/ticket/263</a>&gt;: "text about historical percent-decoding unclear"
1063               </li>
1064               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/264">http://tools.ietf.org/wg/httpbis/trac/ticket/264</a>&gt;: "add explanation of language tagging"
1065               </li>
1066               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/265">http://tools.ietf.org/wg/httpbis/trac/ticket/265</a>&gt;: "Clarify that C-D spec does not apply to multipart upload"
1067               </li>
1068            </ul>
1069         </div>
1070         <div id="changes.since.04">
1071            <h2 id="rfc.section.E.9"><a href="#rfc.section.E.9">E.9</a>&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-content-disp-04</a></h2>
1072            <p id="rfc.section.E.9.p.1">Updated implementation information (Chrome 9 implements RFC 5987, IE 9 RC implements it for UTF-8 only).</p>
1073            <p id="rfc.section.E.9.p.2">Clarify who requirements are on, add a section discussing conformance and handling of invalid field values in general.</p>
1074            <p id="rfc.section.E.9.p.3">Closed issues: </p>
1075            <ul>
1076               <li>&lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/243">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/243</a>&gt;: "avoid stating ISO-8859-1 default for header param" (the default is still mentioned, but it was clarified what it applies
1077                  to).
1078               </li>
1079               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/272">http://tools.ietf.org/wg/httpbis/trac/ticket/272</a>&gt;: "Path Separator Characters"
1080               </li>
1081            </ul>
1082         </div>
1083         <div id="changes.since.05">
1084            <h2 id="rfc.section.E.10"><a href="#rfc.section.E.10">E.10</a>&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-content-disp-05</a></h2>
1085            <p id="rfc.section.E.10.p.1">Editorial changes: Fixed two typos where the new Conformance section said "Content-Location" instead of "Content-Disposition".
1086               Cleaned up terminology ("user agent", "recipient", "sender", "message body", ...). Stated what the escape character for quoted-string
1087               is. Explained a use case for "inline" disposition type. Updated implementation notes with respect to the fallback behavior.
1088            </p>
1089            <p id="rfc.section.E.10.p.2">Added appendix "Advice on Generating Content-Disposition Header Fields".</p>
1090         </div>
1091         <div id="changes.since.06">
1092            <h2 id="rfc.section.E.11"><a href="#rfc.section.E.11">E.11</a>&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-content-disp-06</a></h2>
1093            <p id="rfc.section.E.11.p.1">Closed issues: </p>
1094            <ul>
1095               <li>&lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/278">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/278</a>&gt;: "conformance language"
1096               </li>
1097            </ul>
1098         </div>
1099      </div>
1100      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
1101      <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>
1102      </p>
1103      <div class="print2col">
1104         <ul class="ind">
1105            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
1106                  <li>Content-Disposition header field&nbsp;&nbsp;<a href="#rfc.iref.c.1"><b>4</b></a>, <a href="#rfc.xref.header.field.definition.1">8.2</a></li>
1107               </ul>
1108            </li>
1109            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
1110                  <li>Header Fields&nbsp;&nbsp;
1111                     <ul>
1112                        <li>Content-Disposition&nbsp;&nbsp;<a href="#rfc.iref.h.1"><b>4</b></a>, <a href="#rfc.xref.header.field.definition.1">8.2</a></li>
1113                     </ul>
1114                  </li>
1115               </ul>
1116            </li>
1117            <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul>
1118                  <li><em>ISO-8859-1</em>&nbsp;&nbsp;<a href="#rfc.xref.ISO-8859-1.1">4.3</a>, <a href="#ISO-8859-1"><b>10.1</b></a>, <a href="#rfc.xref.ISO-8859-1.2">C</a></li>
1119               </ul>
1120            </li>
1121            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
1122                  <li><em>RFC2046</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">4.3</a>, <a href="#RFC2046"><b>10.2</b></a></li>
1123                  <li><em>RFC2047</em>&nbsp;&nbsp;<a href="#RFC2047"><b>10.2</b></a>, <a href="#rfc.xref.RFC2047.1">C.1</a><ul>
1124                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2047.1">C.1</a></li>
1125                     </ul>
1126                  </li>
1127                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">2</a>, <a href="#RFC2119"><b>10.1</b></a></li>
1128                  <li><em>RFC2183</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2183.1">1</a>, <a href="#rfc.xref.RFC2183.2">4.2</a>, <a href="#rfc.xref.RFC2183.3">4.4</a>, <a href="#rfc.xref.RFC2183.4">4.5</a>, <a href="#rfc.xref.RFC2183.5">8.1</a>, <a href="#RFC2183"><b>10.2</b></a>, <a href="#rfc.xref.RFC2183.6">A</a>, <a href="#rfc.xref.RFC2183.7">B</a><ul>
1129                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2183.7">B</a></li>
1130                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2183.6">A</a></li>
1131                        <li><em>Section 2.8</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2183.2">4.2</a>, <a href="#rfc.xref.RFC2183.3">4.4</a></li>
1132                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2183.4">4.5</a>, <a href="#rfc.xref.RFC2183.5">8.1</a></li>
1133                     </ul>
1134                  </li>
1135                  <li><em>RFC2231</em>&nbsp;&nbsp;<a href="#RFC2231"><b>10.2</b></a>, <a href="#rfc.xref.RFC2231.1">C</a></li>
1136                  <li><em>RFC2388</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2388.1">1</a>, <a href="#RFC2388"><b>10.2</b></a></li>
1137                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">1</a>, <a href="#rfc.xref.RFC2616.3">2</a>, <a href="#rfc.xref.RFC2616.4">4.1</a>, <a href="#rfc.xref.RFC2616.5">4.1</a>, <a href="#rfc.xref.RFC2616.6">4.1</a>, <a href="#rfc.xref.RFC2616.7">4.1</a>, <a href="#rfc.xref.RFC2616.8">4.1</a>, <a href="#rfc.xref.RFC2616.9">7</a>, <a href="#RFC2616"><b>10.1</b></a>, <a href="#rfc.xref.RFC2616.10">A</a>, <a href="#rfc.xref.RFC2616.11">C</a><ul>
1138                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.3">2</a>, <a href="#rfc.xref.RFC2616.8">4.1</a></li>
1139                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.5">4.1</a>, <a href="#rfc.xref.RFC2616.6">4.1</a>, <a href="#rfc.xref.RFC2616.11">C</a></li>
1140                        <li><em>Section 3.6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.7">4.1</a></li>
1141                        <li><em>Section 15.5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.2">1</a></li>
1142                        <li><em>Section 15</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.9">7</a></li>
1143                        <li><em>Section 19.5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.10">A</a></li>
1144                     </ul>
1145                  </li>
1146                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">8.2</a>, <a href="#RFC3864"><b>10.2</b></a></li>
1147                  <li><em>RFC3986</em>&nbsp;&nbsp;<a href="#RFC3986"><b>10.2</b></a>, <a href="#rfc.xref.RFC3986.1">C.2</a><ul>
1148                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.1">C.2</a></li>
1149                     </ul>
1150                  </li>
1151                  <li><em>RFC5987</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.1">4.1</a>, <a href="#rfc.xref.RFC5987.2">4.1</a>, <a href="#rfc.xref.RFC5987.3">4.3</a>, <a href="#rfc.xref.RFC5987.4">5</a>, <a href="#rfc.xref.RFC5987.5">6</a>, <a href="#rfc.xref.RFC5987.6">7</a>, <a href="#rfc.xref.RFC5987.7">7</a>, <a href="#RFC5987"><b>10.1</b></a>, <a href="#rfc.xref.RFC5987.8">A</a>, <a href="#rfc.xref.RFC5987.9">C</a><ul>
1152                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.2">4.1</a></li>
1153                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.7">7</a></li>
1154                     </ul>
1155                  </li>
1156               </ul>
1157            </li>
1158         </ul>
1159      </div>
1160      <div class="avoidbreak">
1161         <h1 id="rfc.authors"><a href="#rfc.authors">Author's Address</a></h1>
1162         <p><b>Julian F. Reschke</b><br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Email: <a href="mailto:julian.reschke@greenbytes.de">julian.reschke@greenbytes.de</a><br>URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a></p>
1163      </div>
1164   </body>
1165</html>
Note: See TracBrowser for help on using the repository browser.