Changeset 2726 for draft-ietf-httpbis-content-disp/01
- Timestamp:
- 14/06/14 11:20:37 (8 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis-content-disp/01/draft-ietf-httpbis-content-disp.html
r1013 r2726 2 2 PUBLIC "-//W3C//DTD HTML 4.01//EN"> 3 3 <html lang="en"> 4 <head profile="http:// www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">4 <head profile="http://dublincore.org/documents/2008/08/04/dc-html/"> 5 5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> 6 6 <title>Use of the Content-Disposition Header Field … … 33 33 body { 34 34 color: black; 35 font-family: verdana, helvetica, arial, sans-serif; 36 font-size: 10pt; 35 font-family: cambria, helvetica, arial, sans-serif; 36 font-size: 11pt; 37 margin-right: 2em; 37 38 } 38 39 cite { 39 40 font-style: normal; 40 41 } 41 dd {42 margin-right: 2em;43 }44 42 dl { 45 43 margin-left: 2em; 46 44 } 47 48 45 ul.empty { 49 46 list-style-type: none; … … 59 56 } 60 57 h1 { 61 font-size: 1 4pt;58 font-size: 130%; 62 59 line-height: 21pt; 63 60 page-break-after: avoid; … … 66 63 page-break-before: always; 67 64 } 68 h1 a {69 color: #333333;70 }71 65 h2 { 72 font-size: 12 pt;66 font-size: 120%; 73 67 line-height: 15pt; 74 68 page-break-after: avoid; 75 69 } 76 h3 , h4, h5, h6{77 font-size: 1 0pt;70 h3 { 71 font-size: 110%; 78 72 page-break-after: avoid; 79 73 } 80 h2 a, h3 a, h4 a, h5 a, h6 a { 74 h4, h5, h6 { 75 page-break-after: avoid; 76 } 77 h1 a, h2 a, h3 a, h4 a, h5 a, h6 a { 81 78 color: black; 82 79 } … … 86 83 li { 87 84 margin-left: 2em; 88 margin-right: 2em;89 85 } 90 86 ol { 91 87 margin-left: 2em; 92 margin-right: 2em; 88 } 89 ol.la { 90 list-style-type: lower-alpha; 91 } 92 ol.ua { 93 list-style-type: upper-alpha; 93 94 } 94 95 ol p { … … 97 98 p { 98 99 margin-left: 2em; 99 margin-right: 2em;100 100 } 101 101 pre { … … 103 103 background-color: lightyellow; 104 104 padding: .25em; 105 page-break-inside: avoid; 105 106 } 106 107 pre.text2 { … … 131 132 table.tt { 132 133 vertical-align: top; 134 border-color: gray; 135 } 136 table.tt th { 137 border-color: gray; 138 } 139 table.tt td { 140 border-color: gray; 141 } 142 table.all { 143 border-style: solid; 144 border-width: 2px; 133 145 } 134 146 table.full { 135 border-style: outset; 136 border-width: 1px; 137 } 138 table.headers { 139 border-style: outset; 140 border-width: 1px; 147 border-style: solid; 148 border-width: 2px; 141 149 } 142 150 table.tt td { 143 151 vertical-align: top; 144 152 } 153 table.all td { 154 border-style: solid; 155 border-width: 1px; 156 } 145 157 table.full td { 146 border-style: inset;158 border-style: none solid; 147 159 border-width: 1px; 148 160 } … … 150 162 vertical-align: top; 151 163 } 164 table.all th { 165 border-style: solid; 166 border-width: 1px; 167 } 152 168 table.full th { 153 border-style: inset;154 border-width: 1px ;169 border-style: solid; 170 border-width: 1px 1px 2px 1px; 155 171 } 156 172 table.headers th { 157 border-style: none none insetnone;158 border-width: 1px;173 border-style: none none solid none; 174 border-width: 2px; 159 175 } 160 176 table.left { … … 171 187 caption-side: bottom; 172 188 font-weight: bold; 173 font-size: 9pt;189 font-size: 10pt; 174 190 margin-top: .5em; 175 191 } … … 178 194 border-spacing: 1px; 179 195 width: 95%; 180 font-size: 1 0pt;196 font-size: 11pt; 181 197 color: white; 182 198 } … … 186 202 td.topnowrap { 187 203 vertical-align: top; 188 white-space: nowrap; 204 white-space: nowrap; 189 205 } 190 206 table.header td { … … 203 219 display:table-header-group; 204 220 } 205 ul.toc {221 ul.toc, ul.toc ul { 206 222 list-style: none; 207 223 margin-left: 1.5em; 208 margin-right: 0em;209 224 padding-left: 0em; 210 225 } 211 li.tocline0{226 ul.toc li { 212 227 line-height: 150%; 213 228 font-weight: bold; 229 margin-left: 0em; 230 } 231 ul.toc li li { 232 line-height: normal; 233 font-weight: normal; 214 234 font-size: 10pt; 215 235 margin-left: 0em; 216 margin-right: 0em; 217 } 218 li.tocline1 { 219 line-height: normal; 220 font-weight: normal; 221 font-size: 9pt; 222 margin-left: 0em; 223 margin-right: 0em; 224 } 225 li.tocline2 { 236 } 237 li.excluded { 226 238 font-size: 0pt; 227 239 } … … 229 241 margin-left: 0em; 230 242 } 231 ul.ind { 243 .title, .filename, h1, h2, h3, h4 { 244 font-family: candara, helvetica, arial, sans-serif; 245 } 246 samp, tt, code, pre { 247 font: consolas, monospace; 248 } 249 ul.ind, ul.ind ul { 232 250 list-style: none; 233 251 margin-left: 1.5em; 234 margin-right: 0em;235 252 padding-left: 0em; 236 253 page-break-before: avoid; 237 254 } 238 li.indline0{255 ul.ind li { 239 256 font-weight: bold; 240 257 line-height: 200%; 241 258 margin-left: 0em; 242 margin-right: 0em; 243 } 244 li.indline1 { 259 } 260 ul.ind li li { 245 261 font-weight: normal; 246 262 line-height: 150%; 247 263 margin-left: 0em; 248 margin-right: 0em;249 264 } 250 265 .avoidbreak { … … 273 288 font-weight: bold; 274 289 text-align: center; 275 font-size: 9pt;290 font-size: 10pt; 276 291 } 277 292 .filename { 278 293 color: #333333; 294 font-size: 75%; 279 295 font-weight: bold; 280 font-size: 12pt;281 296 line-height: 21pt; 282 297 text-align: center; … … 285 300 font-weight: bold; 286 301 } 287 .hidden {288 display: none;289 }290 302 .left { 291 303 text-align: left; … … 295 307 } 296 308 .title { 297 color: #990000;298 font-size: 1 8pt;309 color: green; 310 font-size: 150%; 299 311 line-height: 18pt; 300 312 font-weight: bold; … … 302 314 margin-top: 36pt; 303 315 } 304 .vcardline {305 display: block;306 }307 316 .warning { 308 font-size: 1 4pt;317 font-size: 130%; 309 318 background-color: yellow; 310 319 } … … 315 324 display: none; 316 325 } 317 326 318 327 a { 319 328 color: black; … … 330 339 background-color: white; 331 340 vertical-align: top; 332 font-size: 1 2pt;333 } 334 335 ul.toc a: :after {341 font-size: 110%; 342 } 343 344 ul.toc a:nth-child(2)::after { 336 345 content: leader('.') target-counter(attr(href), page); 337 346 } 338 339 a.iref{347 348 ul.ind li li a { 340 349 content: target-counter(attr(href), page); 341 350 } 342 351 343 352 .print2col { 344 353 column-count: 2; … … 350 359 @page { 351 360 @top-left { 352 content: "Internet-Draft"; 353 } 361 content: "Internet-Draft"; 362 } 354 363 @top-right { 355 content: "September 2010"; 356 } 364 content: "September 2010"; 365 } 357 366 @top-center { 358 content: "Content-Disposition in HTTP"; 359 } 367 content: "Content-Disposition in HTTP"; 368 } 360 369 @bottom-left { 361 content: "Reschke"; 362 } 370 content: "Reschke"; 371 } 363 372 @bottom-center { 364 content: " Standards Track";365 } 373 content: "Expires March 20, 2011"; 374 } 366 375 @bottom-right { 367 content: "[Page " counter(page) "]"; 368 } 369 } 370 371 @page:first { 376 content: "[Page " counter(page) "]"; 377 } 378 } 379 380 @page:first { 372 381 @top-left { 373 382 content: normal; … … 397 406 <link rel="Appendix" title="C Alternative Approaches to Internationalization" href="#rfc.section.C"> 398 407 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 399 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1. 522, 2010-08-31 15:02:33, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">408 <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/"> 400 409 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 401 410 <meta name="dct.creator" content="Reschke, J. F."> … … 417 426 </tr> 418 427 <tr> 419 <td class="left">Updates: <a href="http ://tools.ietf.org/html/rfc2616">2616</a> (if approved)428 <td class="left">Updates: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved) 420 429 </td> 421 430 <td class="right">September 16, 2010</td> … … 432 441 </table> 433 442 <p class="title">Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)<br><span class="filename">draft-ietf-httpbis-content-disp-01</span></p> 434 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 443 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 435 444 <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 445 This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization 437 446 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> 447 </p> 448 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor before publication)</a></h1> 440 449 <p>This specification is expected to replace the definition of Content-Disposition in the HTTP/1.1 specification, as currently 441 450 revised by the IETF HTTPbis working group. See also <<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/123">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/123</a>>. 442 </p> 451 </p> 443 452 <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues 444 453 list is at <<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>> and related documents (including fancy diffs) can be found at <<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>>. 445 </p> 454 </p> 446 455 <p>The changes in this draft are summarized in <a href="#changes.since.00" title="Since draft-ietf-httpbis-content-disp-00">Appendix D.5</a>. 447 </p>448 <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>449 <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>450 <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute451 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>.452 456 </p> 453 <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other 454 documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work 455 in progress”. 456 </p> 457 <p>This Internet-Draft will expire on March 20, 2011.</p> 458 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 459 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 460 <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 461 and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License 462 text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified 463 BSD License. 464 </p> 457 <div id="rfc.status"> 458 <h1><a href="#rfc.status">Status of This Memo</a></h1> 459 <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p> 460 <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute 461 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>. 462 </p> 463 <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other 464 documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work 465 in progress”. 466 </p> 467 <p>This Internet-Draft will expire on March 20, 2011.</p> 468 </div> 469 <div id="rfc.copyrightnotice"> 470 <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1> 471 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 472 <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 473 and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License 474 text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified 475 BSD License. 476 </p> 477 </div> 465 478 <hr class="noprint"> 466 479 <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1> 467 480 <ul class="toc"> 468 <li class="tocline0">1. <a href="#introduction">Introduction</a></li>469 <li class="tocline0">2. <a href="#rfc.section.2">Notational Conventions</a></li>470 <li class="tocline0">3. <a href="#header.field.definition">Header Field Definition</a><ul class="toc">471 <li class="tocline1">3.1 <a href="#rfc.section.3.1">Grammar</a></li>472 <li class="tocline1">3.2 <a href="#disposition.type">Disposition Type</a></li>473 <li class="tocline1">3.3 <a href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></li>474 <li class="tocline1">3.4 <a href="#disposition.parameter.extensions">Disposition Parameter: Extensions</a></li>475 <li class="tocline1">3.5 <a href="#extensibility">Extensibility</a></li>481 <li><a href="#rfc.section.1">1.</a> <a href="#introduction">Introduction</a></li> 482 <li><a href="#rfc.section.2">2.</a> <a href="#rfc.section.2">Notational Conventions</a></li> 483 <li><a href="#rfc.section.3">3.</a> <a href="#header.field.definition">Header Field Definition</a><ul> 484 <li><a href="#rfc.section.3.1">3.1</a> <a href="#rfc.section.3.1">Grammar</a></li> 485 <li><a href="#rfc.section.3.2">3.2</a> <a href="#disposition.type">Disposition Type</a></li> 486 <li><a href="#rfc.section.3.3">3.3</a> <a href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></li> 487 <li><a href="#rfc.section.3.4">3.4</a> <a href="#disposition.parameter.extensions">Disposition Parameter: Extensions</a></li> 488 <li><a href="#rfc.section.3.5">3.5</a> <a href="#extensibility">Extensibility</a></li> 476 489 </ul> 477 490 </li> 478 <li class="tocline0">4. <a href="#examples">Examples</a></li>479 <li class="tocline0">5. <a href="#i18n">Internationalization Considerations</a></li>480 <li class="tocline0">6. <a href="#security.considerations">Security Considerations</a></li>481 <li class="tocline0">7. <a href="#iana.considerations">IANA Considerations</a><ul class="toc">482 <li class="tocline1">7.1 <a href="#registry">Registry for Disposition Values and Parameter</a></li>483 <li class="tocline1">7.2 <a href="#header.field.registration">Header Field Registration</a></li>491 <li><a href="#rfc.section.4">4.</a> <a href="#examples">Examples</a></li> 492 <li><a href="#rfc.section.5">5.</a> <a href="#i18n">Internationalization Considerations</a></li> 493 <li><a href="#rfc.section.6">6.</a> <a href="#security.considerations">Security Considerations</a></li> 494 <li><a href="#rfc.section.7">7.</a> <a href="#iana.considerations">IANA Considerations</a><ul> 495 <li><a href="#rfc.section.7.1">7.1</a> <a href="#registry">Registry for Disposition Values and Parameter</a></li> 496 <li><a href="#rfc.section.7.2">7.2</a> <a href="#header.field.registration">Header Field Registration</a></li> 484 497 </ul> 485 498 </li> 486 <li class="tocline0">8. <a href="#rfc.section.8">Acknowledgements</a></li>487 <li class="tocline0">9. <a href="#rfc.references">References</a><ul class="toc">488 <li class="tocline1">9.1 <a href="#rfc.references.1">Normative References</a></li>489 <li class="tocline1">9.2 <a href="#rfc.references.2">Informative References</a></li>499 <li><a href="#rfc.section.8">8.</a> <a href="#rfc.section.8">Acknowledgements</a></li> 500 <li><a href="#rfc.section.9">9.</a> <a href="#rfc.references">References</a><ul> 501 <li><a href="#rfc.section.9.1">9.1</a> <a href="#rfc.references.1">Normative References</a></li> 502 <li><a href="#rfc.section.9.2">9.2</a> <a href="#rfc.references.2">Informative References</a></li> 490 503 </ul> 491 504 </li> 492 <li class="tocline0"><a href="#rfc.authors">Author's Address</a></li> 493 <li class="tocline0">A. <a href="#changes.from.rfc2616">Changes from the RFC 2616 Definition</a></li> 494 <li class="tocline0">B. <a href="#diffs.compared.to.rfc2183">Differences compared to RFC 2183</a></li> 495 <li class="tocline0">C. <a href="#alternatives">Alternative Approaches to Internationalization</a><ul class="toc"> 496 <li class="tocline1">C.1 <a href="#alternatives.rfc2047">RFC 2047 Encoding</a></li> 497 <li class="tocline1">C.2 <a href="#alternatives.percent">Percent Encoding</a></li> 498 <li class="tocline1">C.3 <a href="#alternatives.sniff">Encoding Sniffing</a></li> 499 <li class="tocline1">C.4 <a href="#alternatives.implementations">Implementations (to be removed by RFC Editor before publication)</a></li> 505 <li><a href="#rfc.section.A">A.</a> <a href="#changes.from.rfc2616">Changes from the RFC 2616 Definition</a></li> 506 <li><a href="#rfc.section.B">B.</a> <a href="#diffs.compared.to.rfc2183">Differences compared to RFC 2183</a></li> 507 <li><a href="#rfc.section.C">C.</a> <a href="#alternatives">Alternative Approaches to Internationalization</a><ul> 508 <li><a href="#rfc.section.C.1">C.1</a> <a href="#alternatives.rfc2047">RFC 2047 Encoding</a></li> 509 <li><a href="#rfc.section.C.2">C.2</a> <a href="#alternatives.percent">Percent Encoding</a></li> 510 <li><a href="#rfc.section.C.3">C.3</a> <a href="#alternatives.sniff">Encoding Sniffing</a></li> 511 <li><a href="#rfc.section.C.4">C.4</a> <a href="#alternatives.implementations">Implementations (to be removed by RFC Editor before publication)</a></li> 500 512 </ul> 501 513 </li> 502 <li class="tocline0">D. <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">503 <li class="tocline1">D.1 <a href="#rfc.section.D.1">Since draft-reschke-rfc2183-in-http-00</a></li>504 <li class="tocline1">D.2 <a href="#rfc.section.D.2">Since draft-reschke-rfc2183-in-http-01</a></li>505 <li class="tocline1">D.3 <a href="#rfc.section.D.3">Since draft-reschke-rfc2183-in-http-02</a></li>506 <li class="tocline1">D.4 <a href="#rfc.section.D.4">Since draft-reschke-rfc2183-in-http-03</a></li>507 <li class="tocline1">D.5 <a href="#changes.since.00">Since draft-ietf-httpbis-content-disp-00</a></li>514 <li><a href="#rfc.section.D">D.</a> <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul> 515 <li><a href="#rfc.section.D.1">D.1</a> <a href="#rfc.section.D.1">Since draft-reschke-rfc2183-in-http-00</a></li> 516 <li><a href="#rfc.section.D.2">D.2</a> <a href="#rfc.section.D.2">Since draft-reschke-rfc2183-in-http-01</a></li> 517 <li><a href="#rfc.section.D.3">D.3</a> <a href="#rfc.section.D.3">Since draft-reschke-rfc2183-in-http-02</a></li> 518 <li><a href="#rfc.section.D.4">D.4</a> <a href="#rfc.section.D.4">Since draft-reschke-rfc2183-in-http-03</a></li> 519 <li><a href="#rfc.section.D.5">D.5</a> <a href="#changes.since.00">Since draft-ietf-httpbis-content-disp-00</a></li> 508 520 </ul> 509 521 </li> 510 <li class="tocline0"><a href="#rfc.index">Index</a></li> 522 <li><a href="#rfc.index">Index</a></li> 523 <li><a href="#rfc.authors">Author's Address</a></li> 511 524 </ul> 512 <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <a id="introduction" href="#introduction">Introduction</a></h1> 513 <p id="rfc.section.1.p.1">HTTP/1.1 defines the Content-Disposition response header field in <a href="http://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="http://tools.ietf.org/html/rfc2616#section-15.5" id="rfc.xref.RFC2616.2">Section 15.5</a>): 514 </p> 515 <blockquote id="rfc.section.1.p.2" cite="http://tools.ietf.org/html/rfc2616#section-15.5"> 516 <p>Content-Disposition is not part of the HTTP standard, but since it is widely implemented, we are documenting its use and risks 517 for implementers. 518 </p> 519 </blockquote> 520 <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 521 testing with existing User Agents, it fully defines a profile of the features defined in the Multipurpose Internet Mail Extensions 522 (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. 523 </p> 524 <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> Notational Conventions 525 </h1> 526 <p id="rfc.section.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" 527 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>. 528 </p> 529 <p id="rfc.section.2.p.2">This specification uses the augmented BNF notation defined in <a href="http://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 linear whitespace (LWS). 530 </p> 531 <div id="rfc.iref.h.1"></div> 532 <div id="rfc.iref.c.1"></div> 533 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="header.field.definition" href="#header.field.definition">Header Field Definition</a></h1> 534 <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, 535 and also can be used to attach additional metadata, such as the filename. 536 </p> 537 <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a> Grammar 538 </h2> 539 <div id="rfc.figure.u.1"></div><pre class="inline"> content-disposition = "Content-Disposition" ":" 525 <div id="introduction"> 526 <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <a href="#introduction">Introduction</a></h1> 527 <p id="rfc.section.1.p.1">HTTP/1.1 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>): 528 </p> 529 <blockquote id="rfc.section.1.p.2" cite="http://tools.ietf.org/html/rfc2616#section-15.5"> 530 <p>Content-Disposition is not part of the HTTP standard, but since it is widely implemented, we are documenting its use and risks 531 for implementers. 532 </p> 533 </blockquote> 534 <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 535 testing with existing User Agents, it fully defines a profile of the features defined in the Multipurpose Internet Mail Extensions 536 (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. 537 </p> 538 </div> 539 <div> 540 <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> Notational Conventions 541 </h1> 542 <p id="rfc.section.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" 543 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>. 544 </p> 545 <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 linear whitespace (LWS). 546 </p> 547 </div> 548 <div id="header.field.definition"> 549 <div id="rfc.iref.h.1"></div> 550 <div id="rfc.iref.c.1"></div> 551 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a href="#header.field.definition">Header Field Definition</a></h1> 552 <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, 553 and also can be used to attach additional metadata, such as the filename. 554 </p> 555 <div> 556 <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a> Grammar 557 </h2> 558 <div id="rfc.figure.u.1"></div><pre class="inline"> content-disposition = "Content-Disposition" ":" 540 559 disposition-type *( ";" disposition-parm ) 541 560 … … 552 571 | ext-token "=" ext-value 553 572 ext-token = <the characters in token, followed by "*"> 554 </pre><div id="rfc.figure.u.2"></div> 555 <p>Defined in <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>: 556 </p> <pre class="inline"> token = <token, defined in <a href="#RFC2616" id="rfc.xref.RFC2616.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>> 557 value = <value, defined in <a href="#RFC2616" id="rfc.xref.RFC2616.6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-3.6">Section 3.6</a>> 558 </pre><div id="rfc.figure.u.3"></div> 559 <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>: 560 </p> <pre class="inline"> ext-value = <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="http://tools.ietf.org/html/rfc5987#section-3.2">Section 3.2</a>> 561 </pre><h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="disposition.type" href="#disposition.type">Disposition Type</a></h2> 562 <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 563 response, but directly enter a "save as..." dialog. 564 </p> 565 <p id="rfc.section.3.2.p.2">On the other hand, if it matches "inline" (case-insensitively), this implies default processing.</p> 566 <p id="rfc.section.3.2.p.3">Unknown or unhandled 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="http://tools.ietf.org/html/rfc2183#section-2.8">Section 2.8</a>). 567 </p> 568 <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a> <a id="disposition.parameter.filename" href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></h2> 569 <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 570 for storing the message payload. 571 </p> 572 <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 573 "attachment" disposition type), or later on (for instance, when the user decides to save the contents of the current page 574 being displayed). 575 </p> 576 <p id="rfc.section.3.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>). 577 </p> 578 <p id="rfc.section.3.3.p.4">Many user agent implementations predating this specification do not understand the "filename*" parameter. Therefore, when 579 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 580 more expressive "filename*" parameter, and the "filename" parameter as fallback for legacy recipients (see <a href="#examples" title="Examples">Section 4</a> for an example). 581 </p> 582 <p id="rfc.section.3.3.p.5">It is essential that user agents treat the specified filename as advisory only, thus be very careful in extracting the desired 583 information. In particular: 584 </p> 585 <ul> 586 <li> 587 <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"). 588 </p> 589 </li> 590 <li> 591 <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 592 extension could introduce a privilege escalation when later on the file is opened locally (consider ".exe"). Thus, recipients 593 need to ensure that a file extension is used that is safe, optimally matching the media type of the received payload. 594 </p> 595 </li> 596 <li> 597 <p>Other aspects recipients need to be aware of are names that have a special meaning in the file system or in shell commands, 598 such as "." and "..", "~", "|", and also device names. 599 </p> 600 </li> 601 </ul> 602 <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a> <a id="disposition.parameter.extensions" href="#disposition.parameter.extensions">Disposition Parameter: Extensions</a></h2> 603 <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="http://tools.ietf.org/html/rfc2183#section-2.8">Section 2.8</a>). 604 </p> 605 <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a> <a id="extensibility" href="#extensibility">Extensibility</a></h2> 606 <p id="rfc.section.3.5.p.1">Note that <a href="http://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 607 using Content-Disposition, such as MIME and HTTP. Therefore, not all registered values may make sense in the context of HTTP. 608 </p> 609 <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="examples" href="#examples">Examples</a></h1> 610 <div id="rfc.figure.u.4"></div> 611 <p>Direct UA to show "save as" dialog, with a filename of "example.html":</p> <pre class="text">Content-Disposition: Attachment; filename=example.html 612 </pre><div id="rfc.figure.u.5"></div> 613 <p>Direct UA to behave as if the Content-Disposition header field wasn't present, but to remember the filename "example.html" 614 for a subsequent save operation: 615 </p> <pre class="text">Content-Disposition: INLINE; FILENAME= "example.html" 616 </pre><div id="rfc.figure.u.6"></div> 617 <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 618 </pre> <p>Note that this example uses the extended 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> to specify that the natural language of the filename is English, and also to encode the space character which is not allowed 619 in the token production. 620 </p> 621 <div id="rfc.figure.u.7"></div> 622 <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; 573 </pre><div id="rfc.figure.u.2"></div> 574 <p>Defined in <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>: 575 </p><pre class="inline"> token = <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>> 576 value = <value, 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-3.6">Section 3.6</a>> 577 </pre><div id="rfc.figure.u.3"></div> 578 <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>: 579 </p><pre class="inline"> ext-value = <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>> 580 </pre></div> 581 <div id="disposition.type"> 582 <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a href="#disposition.type">Disposition Type</a></h2> 583 <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 584 response, but directly enter a "save as..." dialog. 585 </p> 586 <p id="rfc.section.3.2.p.2">On the other hand, if it matches "inline" (case-insensitively), this implies default processing.</p> 587 <p id="rfc.section.3.2.p.3">Unknown or unhandled 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="https://tools.ietf.org/html/rfc2183#section-2.8">Section 2.8</a>). 588 </p> 589 </div> 590 <div id="disposition.parameter.filename"> 591 <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a> <a href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></h2> 592 <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 593 for storing the message payload. 594 </p> 595 <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 596 "attachment" disposition type), or later on (for instance, when the user decides to save the contents of the current page 597 being displayed). 598 </p> 599 <p id="rfc.section.3.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>). 600 </p> 601 <p id="rfc.section.3.3.p.4">Many user agent implementations predating this specification do not understand the "filename*" parameter. Therefore, when 602 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 603 more expressive "filename*" parameter, and the "filename" parameter as fallback for legacy recipients (see <a href="#examples" title="Examples">Section 4</a> for an example). 604 </p> 605 <p id="rfc.section.3.3.p.5">It is essential that user agents treat the specified filename as advisory only, thus be very careful in extracting the desired 606 information. In particular: 607 </p> 608 <ul> 609 <li> 610 <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"). 611 </p> 612 </li> 613 <li> 614 <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 615 extension could introduce a privilege escalation when later on the file is opened locally (consider ".exe"). Thus, recipients 616 need to ensure that a file extension is used that is safe, optimally matching the media type of the received payload. 617 </p> 618 </li> 619 <li> 620 <p>Other aspects recipients need to be aware of are names that have a special meaning in the file system or in shell commands, 621 such as "." and "..", "~", "|", and also device names. 622 </p> 623 </li> 624 </ul> 625 </div> 626 <div id="disposition.parameter.extensions"> 627 <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a> <a href="#disposition.parameter.extensions">Disposition Parameter: Extensions</a></h2> 628 <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="https://tools.ietf.org/html/rfc2183#section-2.8">Section 2.8</a>). 629 </p> 630 </div> 631 <div id="extensibility"> 632 <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a> <a href="#extensibility">Extensibility</a></h2> 633 <p id="rfc.section.3.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 634 using Content-Disposition, such as MIME and HTTP. Therefore, not all registered values may make sense in the context of HTTP. 635 </p> 636 </div> 637 </div> 638 <div id="examples"> 639 <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a href="#examples">Examples</a></h1> 640 <div id="rfc.figure.u.4"></div> 641 <p>Direct UA to show "save as" dialog, with a filename of "example.html":</p><pre class="text">Content-Disposition: Attachment; filename=example.html 642 </pre><div id="rfc.figure.u.5"></div> 643 <p>Direct UA to behave as if the Content-Disposition header field wasn't present, but to remember the filename "example.html" 644 for a subsequent save operation: 645 </p><pre class="text">Content-Disposition: INLINE; FILENAME= "example.html" 646 </pre><div id="rfc.figure.u.6"></div> 647 <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 648 </pre><p>Note that this example uses the extended 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> to specify that the natural language of the filename is English, and also to encode the space character which is not allowed 649 in the token production. 650 </p> 651 <div id="rfc.figure.u.7"></div> 652 <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; 623 653 filename*= UTF-8''<b>%e2%82%ac</b>%20rates 624 </pre> 625 </p>626 <div id="rfc.figure.u.8"></div>627 <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;654 </pre><p>Here, 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> is also used to encode the non-ISO-8859-1 character. 655 </p> 656 <div id="rfc.figure.u.8"></div> 657 <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; 628 658 filename="EURO rates"; 629 659 filename*=utf-8''<b>%e2%82%ac</b>%20rates 630 </pre> <p>Note: as of September 2010, those user agents that do not support the RFC 5987 encoding ignore "filename*" when it occurs 631 after "filename". Unfortunately, some user agents that do support RFC 5987 do pick the "filename" rather than the "filename*" 632 parameter when it occurs first; it is expected that this situation is going to improve soon. 633 </p> 634 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="i18n" href="#i18n">Internationalization Considerations</a></h1> 635 <p id="rfc.section.5.p.1">The "filename*" parameter (<a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section 3.3</a>), using the 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>, allows the server to transmit characters outside the ISO-8859-1 character set, and also to optionally specify the language 636 in use. 637 </p> 638 <p id="rfc.section.5.p.2">Future parameters might also require internationalization, in which case the same encoding can be used.</p> 639 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> 640 <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 3.3</a>. 641 </p> 642 <p id="rfc.section.6.p.2">Furthermore, implementers also ought to be aware of the Security Considerations applying to HTTP (see <a href="http://tools.ietf.org/html/rfc2616#section-15">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="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a> (see <a href="http://tools.ietf.org/html/rfc5987#section-5" id="rfc.xref.RFC5987.8">Section 5</a>). 643 </p> 644 <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="iana.considerations" href="#iana.considerations">IANA Considerations</a></h1> 645 <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a> <a id="registry" href="#registry">Registry for Disposition Values and Parameter</a></h2> 646 <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 647 are defined in <a href="http://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>. 648 </p> 649 <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a> <a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2> 650 <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 651 (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>). 652 </p> 653 <p id="rfc.section.7.2.p.2"> </p> 654 <dl> 655 <dt>Header field name:</dt> 656 <dd>Content-Disposition</dd> 657 <dt>Applicable protocol:</dt> 658 <dd>http</dd> 659 <dt>Status:</dt> 660 <dd>standard</dd> 661 <dt>Author/Change controller:</dt> 662 <dd>IETF</dd> 663 <dt>Specification document:</dt> 664 <dd>this specification (<a href="#header.field.definition" id="rfc.xref.header.field.definition.1" title="Header Field Definition">Section 3</a>) 665 </dd> 666 </dl> 667 <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> Acknowledgements 668 </h1> 669 <p id="rfc.section.8.p.1">Thanks to Rolf Eike Beer, Bjoern Hoehrmann, Alfred Hoenes, Roar Lauritzsen, and Henrik Nordstrom for their valuable feedback.</p> 660 </pre><p>Note: as of September 2010, those user agents that do not support the RFC 5987 encoding ignore "filename*" when it occurs 661 after "filename". Unfortunately, some user agents that do support RFC 5987 do pick the "filename" rather than the "filename*" 662 parameter when it occurs first; it is expected that this situation is going to improve soon. 663 </p> 664 </div> 665 <div id="i18n"> 666 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a href="#i18n">Internationalization Considerations</a></h1> 667 <p id="rfc.section.5.p.1">The "filename*" parameter (<a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section 3.3</a>), using the 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>, allows the server to transmit characters outside the ISO-8859-1 character set, and also to optionally specify the language 668 in use. 669 </p> 670 <p id="rfc.section.5.p.2">Future parameters might also require internationalization, in which case the same encoding can be used.</p> 671 </div> 672 <div id="security.considerations"> 673 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a href="#security.considerations">Security Considerations</a></h1> 674 <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 3.3</a>. 675 </p> 676 <p id="rfc.section.6.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.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="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.8">Section 5</a>). 677 </p> 678 </div> 679 <div id="iana.considerations"> 680 <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a href="#iana.considerations">IANA Considerations</a></h1> 681 <div id="registry"> 682 <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a> <a href="#registry">Registry for Disposition Values and Parameter</a></h2> 683 <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 684 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>. 685 </p> 686 </div> 687 <div id="header.field.registration"> 688 <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a> <a href="#header.field.registration">Header Field Registration</a></h2> 689 <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 690 (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>). 691 </p> 692 <p id="rfc.section.7.2.p.2"></p> 693 <dl> 694 <dt>Header field name:</dt> 695 <dd>Content-Disposition</dd> 696 <dt>Applicable protocol:</dt> 697 <dd>http</dd> 698 <dt>Status:</dt> 699 <dd>standard</dd> 700 <dt>Author/Change controller:</dt> 701 <dd>IETF</dd> 702 <dt>Specification document:</dt> 703 <dd>this specification (<a href="#header.field.definition" id="rfc.xref.header.field.definition.1" title="Header Field Definition">Section 3</a>) 704 </dd> 705 </dl> 706 </div> 707 </div> 708 <div> 709 <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> Acknowledgements 710 </h1> 711 <p id="rfc.section.8.p.1">Thanks to Rolf Eike Beer, Bjoern Hoehrmann, Alfred Hoenes, Roar Lauritzsen, and Henrik Nordstrom for their valuable feedback.</p> 712 </div> 670 713 <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References 671 714 </h1> 672 715 <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References 673 716 </h2> 674 <table> 717 <table> 675 718 <tr> 676 719 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> … … 679 722 <tr> 680 723 <td class="reference"><b id="RFC2119">[RFC2119]</b></td> 681 <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http ://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP 14, RFC 2119, March 1997.724 <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 14, RFC 2119, March 1997. 682 725 </td> 683 726 </tr> 684 727 <tr> 685 728 <td class="reference"><b id="RFC2616">[RFC2616]</b></td> 686 <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="http ://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC 2616, June 1999.729 <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 2616, June 1999. 687 730 </td> 688 731 </tr> 689 732 <tr> 690 733 <td class="reference"><b id="RFC5987">[RFC5987]</b></td> 691 <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="http ://tools.ietf.org/html/rfc5987">Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters</a>”, RFC 5987, August 2010.734 <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 5987, August 2010. 692 735 </td> 693 736 </tr> … … 695 738 <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References 696 739 </h2> 697 <table> 740 <table> 698 741 <tr> 699 742 <td class="reference"><b id="RFC2046">[RFC2046]</b></td> 700 <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="http ://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC 2046, November 1996.743 <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 2046, November 1996. 701 744 </td> 702 745 </tr> 703 746 <tr> 704 747 <td class="reference"><b id="RFC2047">[RFC2047]</b></td> 705 <td class="top"><a href="mailto:moore@cs.utk.edu" title="University of Tennessee">Moore, K.</a>, “<a href="http ://tools.ietf.org/html/rfc2047">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</a>”, RFC 2047, November 1996.748 <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 2047, November 1996. 706 749 </td> 707 750 </tr> 708 751 <tr> 709 752 <td class="reference"><b id="RFC2183">[RFC2183]</b></td> 710 <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="http ://tools.ietf.org/html/rfc2183">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</a>”, RFC 2183, August 1997.753 <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 2183, August 1997. 711 754 </td> 712 755 </tr> 713 756 <tr> 714 757 <td class="reference"><b id="RFC2231">[RFC2231]</b></td> 715 <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="http ://tools.ietf.org/html/rfc2231">MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations</a>”, RFC 2231, November 1997.758 <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 2231, November 1997. 716 759 </td> 717 760 </tr> 718 761 <tr> 719 762 <td class="reference"><b id="RFC3629">[RFC3629]</b></td> 720 <td class="top"><a href="mailto:fyergeau@alis.com" title="Alis Technologies">Yergeau, F.</a>, “<a href="http ://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>”, STD 63, RFC 3629, November 2003.763 <td class="top"><a href="mailto:fyergeau@alis.com" title="Alis Technologies">Yergeau, F.</a>, “<a href="https://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>”, STD 63, RFC 3629, November 2003. 721 764 </td> 722 765 </tr> 723 766 <tr> 724 767 <td class="reference"><b id="RFC3864">[RFC3864]</b></td> 725 <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="http ://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP 90, RFC 3864, September 2004.768 <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 90, RFC 3864, September 2004. 726 769 </td> 727 770 </tr> 728 771 <tr> 729 772 <td class="reference"><b id="RFC3986">[RFC3986]</b></td> 730 <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="http ://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, STD 66, RFC 3986, January 2005.773 <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 66, RFC 3986, January 2005. 731 774 </td> 732 775 </tr> 733 776 </table> 734 <div class="avoidbreak"> 735 <h1 id="rfc.authors"><a href="#rfc.authors">Author's Address</a></h1> 736 <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> <span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline">Email: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address> 737 </div> 738 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="changes.from.rfc2616" href="#changes.from.rfc2616">Changes from the RFC 2616 Definition</a></h1> 739 <p id="rfc.section.A.p.1">Compared to <a href="http://tools.ietf.org/html/rfc2616#section-19.5.1">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: 740 </p> 741 <ul> 742 <li>According to RFC 2616, the disposition type "attachment" only applies to content of type "application/octet-stream". This 743 restriction has been removed, because user agents in practice do not check the content type, and it also discourages properly 744 declaring the media type. 745 </li> 746 <li>RFC 2616 only allows "quoted-string" for the filename parameter. This would be an exceptional parameter syntax, and also doesn't 747 reflect actual use. 748 </li> 749 <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="http://tools.ietf.org/html/rfc2183#section-2.1">Section 2.1</a>) has been re-added with a suggestion for its processing. 750 </li> 751 <li>This specification requires support for the extended parameter encoding defined 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>. 752 </li> 753 </ul> 754 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="diffs.compared.to.rfc2183" href="#diffs.compared.to.rfc2183">Differences compared to RFC 2183</a></h1> 755 <p id="rfc.section.B.p.1"> <a href="http://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". These 756 do not appear to be implemented by any user agent, thus have been omitted from this specification. 757 </p> 758 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="alternatives" href="#alternatives">Alternative Approaches to Internationalization</a></h1> 759 <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="http://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>). For the "filename" parameter, this of course is an unacceptable restriction. 760 </p> 761 <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 762 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="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>). 763 </p> 764 <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 765 to the RFC 5987 encoding used in this specification. 766 </p> 767 <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a> <a id="alternatives.rfc2047" href="#alternatives.rfc2047">RFC 2047 Encoding</a></h2> 768 <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 769 - see <a href="http://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>: 770 </p> 771 <blockquote id="rfc.section.C.1.p.2" cite="http://tools.ietf.org/html/rfc2047#section-5"> 772 <p>An 'encoded-word' MUST NOT appear within a 'quoted-string'.</p> 773 <p>...</p> 774 <p>An 'encoded-word' MUST NOT be used in parameter of a MIME Content-Type or Content-Disposition field, or in any structured 775 field body except within a 'comment' or 'phrase'. 776 </p> 777 </blockquote> 778 <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 779 confused by it. 780 </p> 781 <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a> <a id="alternatives.percent" href="#alternatives.percent">Percent Encoding</a></h2> 782 <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="http://tools.ietf.org/html/rfc3986#section-2.1">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. 783 </p> 784 <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 785 to the user. 786 </p> 787 <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 788 to use in multi-lingual environments. 789 </p> 790 <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a> <a id="alternatives.sniff" href="#alternatives.sniff">Encoding Sniffing</a></h2> 791 <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 792 the correct interpretation. 793 </p> 794 <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> 795 <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a> <a id="alternatives.implementations" href="#alternatives.implementations">Implementations (to be removed by RFC Editor before publication)</a></h2> 796 <p id="rfc.section.C.4.p.1">Unfortunately, as of September 2010, neither the encoding defined in RFCs 2231 and 5987, nor any of the alternate approaches 797 discussed above was implemented interoperably. Thus, this specification recommends the approach defined in RFC 5987, which 798 at least has the advantage of actually being specified properly. 799 </p> 800 <p id="rfc.section.C.4.p.2">The table below shows the implementation support for the various approaches:</p> 801 <div id="rfc.table.u.1"> 802 <table class="tt full left" cellpadding="3" cellspacing="0"> 803 <thead> 804 <tr> 805 <th>User Agent</th> 806 <th>RFC 2231/5987</th> 807 <th>RFC 2047</th> 808 <th>Percent Encoding</th> 809 <th>Encoding Sniffing</th> 810 </tr> 811 </thead> 812 <tbody> 813 <tr> 814 <td class="left">Chrome</td> 815 <td class="left">no</td> 816 <td class="left">yes</td> 817 <td class="left">yes</td> 818 <td class="left">yes</td> 819 </tr> 820 <tr> 821 <td class="left">Firefox</td> 822 <td class="left">yes (*)</td> 823 <td class="left">yes</td> 824 <td class="left">no</td> 825 <td class="left">yes</td> 826 </tr> 827 <tr> 828 <td class="left">Internet Explorer</td> 829 <td class="left">no</td> 830 <td class="left">no</td> 831 <td class="left">yes</td> 832 <td class="left">no</td> 833 </tr> 834 <tr> 835 <td class="left">Konqueror</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">Opera</td> 843 <td class="left">yes (*)</td> 844 <td class="left">no</td> 845 <td class="left">no</td> 846 <td class="left">no</td> 847 </tr> 848 <tr> 849 <td class="left">Safari</td> 850 <td class="left">no</td> 851 <td class="left">no</td> 852 <td class="left">no</td> 853 <td class="left">yes</td> 854 </tr> 855 </tbody> 856 </table> 857 <p>(*) Does not implement the fallback behavior to "filename" described in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section 3.3</a>. 858 </p> 859 </div> 860 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 861 <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a> Since draft-reschke-rfc2183-in-http-00 862 </h2> 863 <p id="rfc.section.D.1.p.1">Adjust terminology ("header" -> "header field"). Update rfc2231-in-http reference.</p> 864 <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a> Since draft-reschke-rfc2183-in-http-01 865 </h2> 866 <p id="rfc.section.D.2.p.1">Update rfc2231-in-http reference. Actually define the "filename" parameter. Add internationalization considerations. Add examples 867 using the RFC 5987 encoding. Add overview over other approaches, plus a table reporting implementation status. Add and resolve 868 issue "nodep2183". Add issues "asciivsiso", "deplboth", "quoted", and "registry". 869 </p> 870 <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a> Since draft-reschke-rfc2183-in-http-02 871 </h2> 872 <p id="rfc.section.D.3.p.1">Add and close issue "docfallback". Close issues "asciivsiso", "deplboth", "quoted", and "registry".</p> 873 <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a> Since draft-reschke-rfc2183-in-http-03 874 </h2> 875 <p id="rfc.section.D.4.p.1">Updated to be a Working Draft of the IETF HTTPbis Working Group.</p> 876 <h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a> <a id="changes.since.00" href="#changes.since.00">Since draft-ietf-httpbis-content-disp-00</a></h2> 877 <p id="rfc.section.D.5.p.1">Closed issues: </p> 878 <ul> 879 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/242">http://tools.ietf.org/wg/httpbis/trac/ticket/242</a>>: "handling of unknown disposition types" 880 </li> 881 </ul> 882 <p id="rfc.section.D.5.p.2">Slightly updated the notes about the proposed fallback behavior.</p> 777 <div id="changes.from.rfc2616"> 778 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a href="#changes.from.rfc2616">Changes from the RFC 2616 Definition</a></h1> 779 <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.8"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, the following normative changes reflecting actual implementations have been made: 780 </p> 781 <ul> 782 <li>According to RFC 2616, the disposition type "attachment" only applies to content of type "application/octet-stream". This 783 restriction has been removed, because user agents in practice do not check the content type, and it also discourages properly 784 declaring the media type. 785 </li> 786 <li>RFC 2616 only allows "quoted-string" for the filename parameter. This would be an exceptional parameter syntax, and also doesn't 787 reflect actual use. 788 </li> 789 <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. 790 </li> 791 <li>This specification requires support for the extended parameter encoding defined 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>. 792 </li> 793 </ul> 794 </div> 795 <div id="diffs.compared.to.rfc2183"> 796 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a href="#diffs.compared.to.rfc2183">Differences compared to RFC 2183</a></h1> 797 <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". These 798 do not appear to be implemented by any user agent, thus have been omitted from this specification. 799 </p> 800 </div> 801 <div id="alternatives"> 802 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a href="#alternatives">Alternative Approaches to Internationalization</a></h1> 803 <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="https://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>). For the "filename" parameter, this of course is an unacceptable restriction. 804 </p> 805 <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 806 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="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>). 807 </p> 808 <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 809 to the RFC 5987 encoding used in this specification. 810 </p> 811 <div id="alternatives.rfc2047"> 812 <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a> <a href="#alternatives.rfc2047">RFC 2047 Encoding</a></h2> 813 <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 814 - 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>: 815 </p> 816 <blockquote id="rfc.section.C.1.p.2" cite="http://tools.ietf.org/html/rfc2047#section-5"> 817 <p>An 'encoded-word' MUST NOT appear within a 'quoted-string'.</p> 818 <p>...</p> 819 <p>An 'encoded-word' MUST NOT be used in parameter of a MIME Content-Type or Content-Disposition field, or in any structured 820 field body except within a 'comment' or 'phrase'. 821 </p> 822 </blockquote> 823 <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 824 confused by it. 825 </p> 826 </div> 827 <div id="alternatives.percent"> 828 <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a> <a href="#alternatives.percent">Percent Encoding</a></h2> 829 <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 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. 830 </p> 831 <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 832 to the user. 833 </p> 834 <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 835 to use in multi-lingual environments. 836 </p> 837 </div> 838 <div id="alternatives.sniff"> 839 <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a> <a href="#alternatives.sniff">Encoding Sniffing</a></h2> 840 <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 841 the correct interpretation. 842 </p> 843 <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> 844 </div> 845 <div id="alternatives.implementations"> 846 <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a> <a href="#alternatives.implementations">Implementations (to be removed by RFC Editor before publication)</a></h2> 847 <p id="rfc.section.C.4.p.1">Unfortunately, as of September 2010, neither the encoding defined in RFCs 2231 and 5987, nor any of the alternate approaches 848 discussed above was implemented interoperably. Thus, this specification recommends the approach defined in RFC 5987, which 849 at least has the advantage of actually being specified properly. 850 </p> 851 <p id="rfc.section.C.4.p.2">The table below shows the implementation support for the various approaches:</p> 852 <div id="rfc.table.u.1"> 853 <table class="tt full left" cellpadding="3" cellspacing="0"> 854 <thead> 855 <tr> 856 <th>User Agent</th> 857 <th>RFC 2231/5987</th> 858 <th>RFC 2047</th> 859 <th>Percent Encoding</th> 860 <th>Encoding Sniffing</th> 861 </tr> 862 </thead> 863 <tbody> 864 <tr> 865 <td class="left">Chrome</td> 866 <td class="left">no</td> 867 <td class="left">yes</td> 868 <td class="left">yes</td> 869 <td class="left">yes</td> 870 </tr> 871 <tr> 872 <td class="left">Firefox</td> 873 <td class="left">yes (*)</td> 874 <td class="left">yes</td> 875 <td class="left">no</td> 876 <td class="left">yes</td> 877 </tr> 878 <tr> 879 <td class="left">Internet Explorer</td> 880 <td class="left">no</td> 881 <td class="left">no</td> 882 <td class="left">yes</td> 883 <td class="left">no</td> 884 </tr> 885 <tr> 886 <td class="left">Konqueror</td> 887 <td class="left">yes</td> 888 <td class="left">no</td> 889 <td class="left">no</td> 890 <td class="left">no</td> 891 </tr> 892 <tr> 893 <td class="left">Opera</td> 894 <td class="left">yes (*)</td> 895 <td class="left">no</td> 896 <td class="left">no</td> 897 <td class="left">no</td> 898 </tr> 899 <tr> 900 <td class="left">Safari</td> 901 <td class="left">no</td> 902 <td class="left">no</td> 903 <td class="left">no</td> 904 <td class="left">yes</td> 905 </tr> 906 </tbody> 907 </table> 908 <p>(*) Does not implement the fallback behavior to "filename" described in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section 3.3</a>. 909 </p> 910 </div> 911 </div> 912 </div> 913 <div id="change.log"> 914 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 915 <div> 916 <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a> Since draft-reschke-rfc2183-in-http-00 917 </h2> 918 <p id="rfc.section.D.1.p.1">Adjust terminology ("header" -> "header field"). Update rfc2231-in-http reference.</p> 919 </div> 920 <div> 921 <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a> Since draft-reschke-rfc2183-in-http-01 922 </h2> 923 <p id="rfc.section.D.2.p.1">Update rfc2231-in-http reference. Actually define the "filename" parameter. Add internationalization considerations. Add examples 924 using the RFC 5987 encoding. Add overview over other approaches, plus a table reporting implementation status. Add and resolve 925 issue "nodep2183". Add issues "asciivsiso", "deplboth", "quoted", and "registry". 926 </p> 927 </div> 928 <div> 929 <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a> Since draft-reschke-rfc2183-in-http-02 930 </h2> 931 <p id="rfc.section.D.3.p.1">Add and close issue "docfallback". Close issues "asciivsiso", "deplboth", "quoted", and "registry".</p> 932 </div> 933 <div> 934 <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a> Since draft-reschke-rfc2183-in-http-03 935 </h2> 936 <p id="rfc.section.D.4.p.1">Updated to be a Working Draft of the IETF HTTPbis Working Group.</p> 937 </div> 938 <div id="changes.since.00"> 939 <h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a> <a href="#changes.since.00">Since draft-ietf-httpbis-content-disp-00</a></h2> 940 <p id="rfc.section.D.5.p.1">Closed issues: </p> 941 <ul> 942 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/242">http://tools.ietf.org/wg/httpbis/trac/ticket/242</a>>: "handling of unknown disposition types" 943 </li> 944 </ul> 945 <p id="rfc.section.D.5.p.2">Slightly updated the notes about the proposed fallback behavior.</p> 946 </div> 947 </div> 883 948 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 884 949 <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> … … 886 951 <div class="print2col"> 887 952 <ul class="ind"> 888 <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">889 <li class="indline1">Content-Disposition header <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>953 <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul> 954 <li>Content-Disposition header <a href="#rfc.iref.c.1"><b>3</b></a>, <a href="#rfc.xref.header.field.definition.1">7.2</a></li> 890 955 </ul> 891 956 </li> 892 <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">893 <li class="indline1">Headers 894 <ul class="ind">895 <li class="indline1">Content-Disposition <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>957 <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul> 958 <li>Headers 959 <ul> 960 <li>Content-Disposition <a href="#rfc.iref.h.1"><b>3</b></a>, <a href="#rfc.xref.header.field.definition.1">7.2</a></li> 896 961 </ul> 897 962 </li> 898 963 </ul> 899 964 </li> 900 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">901 <li class="indline1"><em>ISO-8859-1</em> <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>965 <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul> 966 <li><em>ISO-8859-1</em> <a href="#rfc.xref.ISO-8859-1.1">3.3</a>, <a href="#ISO-8859-1"><b>9.1</b></a>, <a href="#rfc.xref.ISO-8859-1.2">C</a></li> 902 967 </ul> 903 968 </li> 904 <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">905 <li class="indline1"><em>RFC2046</em> <a class="iref" href="#rfc.xref.RFC2046.1">3.3</a>, <a class="iref"href="#RFC2046"><b>9.2</b></a></li>906 <li class="indline1"><em>RFC2047</em> <a class="iref" href="#RFC2047"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2047.1">C.1</a><ul class="ind">907 <li class="indline1"><em>Section 5</em> <a class="iref"href="#rfc.xref.RFC2047.1">C.1</a></li>969 <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul> 970 <li><em>RFC2046</em> <a href="#rfc.xref.RFC2046.1">3.3</a>, <a href="#RFC2046"><b>9.2</b></a></li> 971 <li><em>RFC2047</em> <a href="#RFC2047"><b>9.2</b></a>, <a href="#rfc.xref.RFC2047.1">C.1</a><ul> 972 <li><em>Section 5</em> <a href="#rfc.xref.RFC2047.1">C.1</a></li> 908 973 </ul> 909 974 </li> 910 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">2</a>, <a class="iref"href="#RFC2119"><b>9.1</b></a></li>911 <li class="indline1"><em>RFC2183</em> <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">912 <li class="indline1"><em>Section 2</em> <a class="iref"href="#rfc.xref.RFC2183.7">B</a></li>913 <li class="indline1"><em>Section 2.1</em> <a class="iref"href="#rfc.xref.RFC2183.6">A</a></li>914 <li class="indline1"><em>Section 2.8</em> <a class="iref" href="#rfc.xref.RFC2183.2">3.2</a>, <a class="iref"href="#rfc.xref.RFC2183.3">3.4</a></li>915 <li class="indline1"><em>Section 9</em> <a class="iref" href="#rfc.xref.RFC2183.4">3.5</a>, <a class="iref"href="#rfc.xref.RFC2183.5">7.1</a></li>975 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">2</a>, <a href="#RFC2119"><b>9.1</b></a></li> 976 <li><em>RFC2183</em> <a href="#rfc.xref.RFC2183.1">1</a>, <a href="#rfc.xref.RFC2183.2">3.2</a>, <a href="#rfc.xref.RFC2183.3">3.4</a>, <a href="#rfc.xref.RFC2183.4">3.5</a>, <a href="#rfc.xref.RFC2183.5">7.1</a>, <a href="#RFC2183"><b>9.2</b></a>, <a href="#rfc.xref.RFC2183.6">A</a>, <a href="#rfc.xref.RFC2183.7">B</a><ul> 977 <li><em>Section 2</em> <a href="#rfc.xref.RFC2183.7">B</a></li> 978 <li><em>Section 2.1</em> <a href="#rfc.xref.RFC2183.6">A</a></li> 979 <li><em>Section 2.8</em> <a href="#rfc.xref.RFC2183.2">3.2</a>, <a href="#rfc.xref.RFC2183.3">3.4</a></li> 980 <li><em>Section 9</em> <a href="#rfc.xref.RFC2183.4">3.5</a>, <a href="#rfc.xref.RFC2183.5">7.1</a></li> 916 981 </ul> 917 982 </li> 918 <li class="indline1"><em>RFC2231</em> <a class="iref" href="#RFC2231"><b>9.2</b></a>, <a class="iref"href="#rfc.xref.RFC2231.1">C</a></li>919 <li class="indline1"><em>RFC2616</em> <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">920 <li class="indline1"><em>Section 2.1</em> <a class="iref"href="#rfc.xref.RFC2616.3">2</a></li>921 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.RFC2616.5">3.1</a>, <a class="iref"href="#rfc.xref.RFC2616.9">C</a></li>922 <li class="indline1"><em>Section 3.6</em> <a class="iref"href="#rfc.xref.RFC2616.6">3.1</a></li>923 <li class="indline1"><em>Section 15.5</em> <a class="iref"href="#rfc.xref.RFC2616.2">1</a></li>924 <li class="indline1"><em>Section 15</em> <a class="iref"href="#rfc.xref.RFC2616.7">6</a></li>925 <li class="indline1"><em>Section 19.5.1</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref"href="#rfc.xref.RFC2616.8">A</a></li>983 <li><em>RFC2231</em> <a href="#RFC2231"><b>9.2</b></a>, <a href="#rfc.xref.RFC2231.1">C</a></li> 984 <li><em>RFC2616</em> <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">3.1</a>, <a href="#rfc.xref.RFC2616.5">3.1</a>, <a href="#rfc.xref.RFC2616.6">3.1</a>, <a href="#rfc.xref.RFC2616.7">6</a>, <a href="#RFC2616"><b>9.1</b></a>, <a href="#rfc.xref.RFC2616.8">A</a>, <a href="#rfc.xref.RFC2616.9">C</a><ul> 985 <li><em>Section 2.1</em> <a href="#rfc.xref.RFC2616.3">2</a></li> 986 <li><em>Section 2.2</em> <a href="#rfc.xref.RFC2616.5">3.1</a>, <a href="#rfc.xref.RFC2616.9">C</a></li> 987 <li><em>Section 3.6</em> <a href="#rfc.xref.RFC2616.6">3.1</a></li> 988 <li><em>Section 15.5</em> <a href="#rfc.xref.RFC2616.2">1</a></li> 989 <li><em>Section 15</em> <a href="#rfc.xref.RFC2616.7">6</a></li> 990 <li><em>Section 19.5.1</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.8">A</a></li> 926 991 </ul> 927 992 </li> 928 <li class="indline1"><em>RFC3629</em> <a class="iref" href="#RFC3629"><b>9.2</b></a>, <a class="iref"href="#rfc.xref.RFC3629.1">C.2</a></li>929 <li class="indline1"><em>RFC3864</em> <a class="iref" href="#rfc.xref.RFC3864.1">7.2</a>, <a class="iref"href="#RFC3864"><b>9.2</b></a></li>930 <li class="indline1"><em>RFC3986</em> <a class="iref" href="#RFC3986"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC3986.1">C.2</a><ul class="ind">931 <li class="indline1"><em>Section 2.1</em> <a class="iref"href="#rfc.xref.RFC3986.1">C.2</a></li>993 <li><em>RFC3629</em> <a href="#RFC3629"><b>9.2</b></a>, <a href="#rfc.xref.RFC3629.1">C.2</a></li> 994 <li><em>RFC3864</em> <a href="#rfc.xref.RFC3864.1">7.2</a>, <a href="#RFC3864"><b>9.2</b></a></li> 995 <li><em>RFC3986</em> <a href="#RFC3986"><b>9.2</b></a>, <a href="#rfc.xref.RFC3986.1">C.2</a><ul> 996 <li><em>Section 2.1</em> <a href="#rfc.xref.RFC3986.1">C.2</a></li> 932 997 </ul> 933 998 </li> 934 <li class="indline1"><em>RFC5987</em> <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">935 <li class="indline1"><em>Section 3.2</em> <a class="iref"href="#rfc.xref.RFC5987.2">3.1</a></li>936 <li class="indline1"><em>Section 5</em> <a class="iref"href="#rfc.xref.RFC5987.8">6</a></li>999 <li><em>RFC5987</em> <a href="#rfc.xref.RFC5987.1">3.1</a>, <a href="#rfc.xref.RFC5987.2">3.1</a>, <a href="#rfc.xref.RFC5987.3">3.3</a>, <a href="#rfc.xref.RFC5987.4">4</a>, <a href="#rfc.xref.RFC5987.5">4</a>, <a href="#rfc.xref.RFC5987.6">5</a>, <a href="#rfc.xref.RFC5987.7">6</a>, <a href="#rfc.xref.RFC5987.8">6</a>, <a href="#RFC5987"><b>9.1</b></a>, <a href="#rfc.xref.RFC5987.9">A</a>, <a href="#rfc.xref.RFC5987.10">C</a><ul> 1000 <li><em>Section 3.2</em> <a href="#rfc.xref.RFC5987.2">3.1</a></li> 1001 <li><em>Section 5</em> <a href="#rfc.xref.RFC5987.8">6</a></li> 937 1002 </ul> 938 1003 </li> … … 941 1006 </ul> 942 1007 </div> 1008 <div class="avoidbreak"> 1009 <h1 id="rfc.authors"><a href="#rfc.authors">Author's Address</a></h1> 1010 <p><b>Julian F. Reschke</b><br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW 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> 1011 </div> 943 1012 </body> 944 1013 </html>
Note: See TracChangeset
for help on using the changeset viewer.