Ignore:
Timestamp:
14/06/14 11:20:37 (6 years ago)
Author:
julian.reschke@…
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis-content-disp/09/draft-ietf-httpbis-content-disp.html

    r1211 r2726  
    22  PUBLIC "-//W3C//DTD HTML 4.01//EN">
    33<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/">
    55      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    66      <title>Use of the Content-Disposition&nbsp;Header&nbsp;Field
     
    3333body {
    3434  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;
    3738}
    3839cite {
     
    4243  margin-left: 2em;
    4344}
    44 dd {
    45   margin-right: 2em;
    46 }
    4745dl {
    4846  margin-left: 2em;
    4947}
    50 
    5148ul.empty {
    5249  list-style-type: none;
     
    6259}
    6360h1 {
    64   font-size: 14pt;
     61  font-size: 130%;
    6562  line-height: 21pt;
    6663  page-break-after: avoid;
     
    6966  page-break-before: always;
    7067}
    71 h1 a {
    72   color: #333333;
    73 }
    7468h2 {
    75   font-size: 12pt;
     69  font-size: 120%;
    7670  line-height: 15pt;
    7771  page-break-after: avoid;
    7872}
    79 h3, h4, h5, h6 {
    80   font-size: 10pt;
     73h3 {
     74  font-size: 110%;
    8175  page-break-after: avoid;
    8276}
    83 h2 a, h3 a, h4 a, h5 a, h6 a {
     77h4, h5, h6 {
     78  page-break-after: avoid;
     79}
     80h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
    8481  color: black;
    8582}
     
    8986li {
    9087  margin-left: 2em;
    91   margin-right: 2em;
    9288}
    9389ol {
    9490  margin-left: 2em;
    95   margin-right: 2em;
    9691}
    9792ol.la {
     
    106101p {
    107102  margin-left: 2em;
    108   margin-right: 2em;
    109103}
    110104pre {
     
    112106  background-color: lightyellow;
    113107  padding: .25em;
     108  page-break-inside: avoid;
    114109}
    115110pre.text2 {
     
    140135table.tt {
    141136  vertical-align: top;
     137  border-color: gray;
     138}
     139table.tt th {
     140  border-color: gray;
     141}
     142table.tt td {
     143  border-color: gray;
     144}
     145table.all {
     146  border-style: solid;
     147  border-width: 2px;
    142148}
    143149table.full {
    144   border-style: outset;
    145   border-width: 1px;
    146 }
    147 table.headers {
    148   border-style: outset;
    149   border-width: 1px;
     150  border-style: solid;
     151  border-width: 2px;
    150152}
    151153table.tt td {
    152154  vertical-align: top;
    153155}
     156table.all td {
     157  border-style: solid;
     158  border-width: 1px;
     159}
    154160table.full td {
    155   border-style: inset;
     161  border-style: none solid;
    156162  border-width: 1px;
    157163}
     
    159165  vertical-align: top;
    160166}
     167table.all th {
     168  border-style: solid;
     169  border-width: 1px;
     170}
    161171table.full th {
    162   border-style: inset;
    163   border-width: 1px;
     172  border-style: solid;
     173  border-width: 1px 1px 2px 1px;
    164174}
    165175table.headers th {
    166   border-style: none none inset none;
    167   border-width: 1px;
     176  border-style: none none solid none;
     177  border-width: 2px;
    168178}
    169179table.left {
     
    180190  caption-side: bottom;
    181191  font-weight: bold;
    182   font-size: 9pt;
     192  font-size: 10pt;
    183193  margin-top: .5em;
    184194}
     
    187197  border-spacing: 1px;
    188198  width: 95%;
    189   font-size: 10pt;
     199  font-size: 11pt;
    190200  color: white;
    191201}
     
    195205td.topnowrap {
    196206  vertical-align: top;
    197   white-space: nowrap; 
     207  white-space: nowrap;
    198208}
    199209table.header td {
     
    215225  list-style: none;
    216226  margin-left: 1.5em;
    217   margin-right: 0em;
    218227  padding-left: 0em;
    219228}
     
    221230  line-height: 150%;
    222231  font-weight: bold;
    223   font-size: 10pt;
    224232  margin-left: 0em;
    225   margin-right: 0em;
    226233}
    227234ul.toc li li {
    228235  line-height: normal;
    229236  font-weight: normal;
    230   font-size: 9pt;
     237  font-size: 10pt;
    231238  margin-left: 0em;
    232   margin-right: 0em;
    233239}
    234240li.excluded {
     
    237243ul p {
    238244  margin-left: 0em;
     245}
     246.title, .filename, h1, h2, h3, h4 {
     247  font-family: candara, helvetica, arial, sans-serif;
     248}
     249samp, tt, code, pre {
     250  font: consolas, monospace;
    239251}
    240252ul.ind, ul.ind ul {
    241253  list-style: none;
    242254  margin-left: 1.5em;
    243   margin-right: 0em;
    244255  padding-left: 0em;
    245256  page-break-before: avoid;
     
    249260  line-height: 200%;
    250261  margin-left: 0em;
    251   margin-right: 0em;
    252262}
    253263ul.ind li li {
     
    255265  line-height: 150%;
    256266  margin-left: 0em;
    257   margin-right: 0em;
    258267}
    259268.avoidbreak {
     
    282291  font-weight: bold;
    283292  text-align: center;
    284   font-size: 9pt;
     293  font-size: 10pt;
    285294}
    286295.filename {
    287296  color: #333333;
     297  font-size: 75%;
    288298  font-weight: bold;
    289   font-size: 12pt;
    290299  line-height: 21pt;
    291300  text-align: center;
     
    294303  font-weight: bold;
    295304}
    296 .hidden {
    297   display: none;
    298 }
    299305.left {
    300306  text-align: left;
     
    304310}
    305311.title {
    306   color: #990000;
    307   font-size: 18pt;
     312  color: green;
     313  font-size: 150%;
    308314  line-height: 18pt;
    309315  font-weight: bold;
     
    311317  margin-top: 36pt;
    312318}
    313 .vcardline {
    314   display: block;
    315 }
    316319.warning {
    317   font-size: 14pt;
     320  font-size: 130%;
    318321  background-color: yellow;
    319322}
     
    324327    display: none;
    325328  }
    326  
     329
    327330  a {
    328331    color: black;
     
    339342    background-color: white;
    340343    vertical-align: top;
    341     font-size: 12pt;
    342   }
    343 
    344   ul.toc a::after {
     344    font-size: 110%;
     345  }
     346
     347  ul.toc a:nth-child(2)::after {
    345348    content: leader('.') target-counter(attr(href), page);
    346349  }
    347  
     350
    348351  ul.ind li li a {
    349352    content: target-counter(attr(href), page);
    350353  }
    351  
     354
    352355  .print2col {
    353356    column-count: 2;
     
    359362@page {
    360363  @top-left {
    361        content: "Internet-Draft"; 
    362   } 
     364       content: "Internet-Draft";
     365  }
    363366  @top-right {
    364        content: "March 2011"; 
    365   } 
     367       content: "March 2011";
     368  }
    366369  @top-center {
    367        content: "Content-Disposition in HTTP"; 
    368   } 
     370       content: "Content-Disposition in HTTP";
     371  }
    369372  @bottom-left {
    370        content: "Reschke"; 
    371   } 
     373       content: "Reschke";
     374  }
    372375  @bottom-center {
    373        content: "Expires September 29, 2011"; 
    374   } 
     376       content: "Expires September 29, 2011";
     377  }
    375378  @bottom-right {
    376        content: "[Page " counter(page) "]"; 
    377   } 
    378 }
    379 
    380 @page:first { 
     379       content: "[Page " counter(page) "]";
     380  }
     381}
     382
     383@page:first {
    381384    @top-left {
    382385      content: normal;
     
    408411      <link rel="Appendix" title="D Advice on Generating Content-Disposition Header Fields" href="#rfc.section.D">
    409412      <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E">
    410       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.543, 2011-02-18 21:03:40, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     413      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    411414      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    412415      <meta name="dct.creator" content="Reschke, J. F.">
     
    428431            </tr>
    429432            <tr>
    430                <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
     433               <td class="left">Updates: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    431434               </td>
    432435               <td class="right">March 28, 2011</td>
     
    443446      </table>
    444447      <p class="title">Use of the Content-Disposition&nbsp;Header&nbsp;Field in the Hypertext&nbsp;Transfer&nbsp;Protocol&nbsp;(HTTP)<br><span class="filename">draft-ietf-httpbis-content-disp-09</span></p>
    445       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
     448      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    446449      <p>RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard.
    447450         This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization
    448451         aspects.
    449       </p> 
    450       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor before publication)</a></h1> 
     452      </p>
     453      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor before publication)</a></h1>
    451454      <p>This specification is expected to replace the definition of Content-Disposition in the HTTP/1.1 specification, as currently
    452455         revised by the IETF HTTPbis working group. See also &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/123">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/123</a>&gt;.
    453       </p> 
     456      </p>
    454457      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    455458         list is at &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/query?component=content-disp">http://trac.tools.ietf.org/wg/httpbis/trac/query?component=content-disp</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
    456       </p> 
     459      </p>
    457460      <p>The changes in this draft are summarized in <a href="#changes.since.08" title="Since draft-ietf-httpbis-content-disp-08">Appendix&nbsp;E.13</a>.
    458       </p>
    459       <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
    460       <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
    461       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
    462          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>.
    463461      </p>
    464       <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
    465          documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
    466          in progress”.
    467       </p>
    468       <p>This Internet-Draft will expire on September 29, 2011.</p>
    469       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    470       <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    471       <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
    472          and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
    473          text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
    474          BSD License.
    475       </p>
     462      <div id="rfc.status">
     463         <h1><a href="#rfc.status">Status of This Memo</a></h1>
     464         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
     465         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
     466            working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
     467         </p>
     468         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     469            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     470            in progress”.
     471         </p>
     472         <p>This Internet-Draft will expire on September 29, 2011.</p>
     473      </div>
     474      <div id="rfc.copyrightnotice">
     475         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     476         <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     477         <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
     478            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
     479            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
     480            BSD License.
     481         </p>
     482      </div>
    476483      <hr class="noprint">
    477484      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    478485      <ul class="toc">
    479          <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a></li>
    480          <li>2.&nbsp;&nbsp;&nbsp;<a href="#notational.conventions">Notational Conventions</a></li>
    481          <li>3.&nbsp;&nbsp;&nbsp;<a href="#conformance.and.error.handling">Conformance and Error Handling</a></li>
    482          <li>4.&nbsp;&nbsp;&nbsp;<a href="#header.field.definition">Header Field Definition</a><ul>
    483                <li>4.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.1">Grammar</a></li>
    484                <li>4.2&nbsp;&nbsp;&nbsp;<a href="#disposition.type">Disposition Type</a></li>
    485                <li>4.3&nbsp;&nbsp;&nbsp;<a href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></li>
    486                <li>4.4&nbsp;&nbsp;&nbsp;<a href="#disposition.parameter.extensions">Disposition Parameter: Extensions</a></li>
    487                <li>4.5&nbsp;&nbsp;&nbsp;<a href="#extensibility">Extensibility</a></li>
     486         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a></li>
     487         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#notational.conventions">Notational Conventions</a></li>
     488         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#conformance.and.error.handling">Conformance and Error Handling</a></li>
     489         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.definition">Header Field Definition</a><ul>
     490               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.1">Grammar</a></li>
     491               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#disposition.type">Disposition Type</a></li>
     492               <li><a href="#rfc.section.4.3">4.3</a>&nbsp;&nbsp;&nbsp;<a href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></li>
     493               <li><a href="#rfc.section.4.4">4.4</a>&nbsp;&nbsp;&nbsp;<a href="#disposition.parameter.extensions">Disposition Parameter: Extensions</a></li>
     494               <li><a href="#rfc.section.4.5">4.5</a>&nbsp;&nbsp;&nbsp;<a href="#extensibility">Extensibility</a></li>
    488495            </ul>
    489496         </li>
    490          <li>5.&nbsp;&nbsp;&nbsp;<a href="#examples">Examples</a></li>
    491          <li>6.&nbsp;&nbsp;&nbsp;<a href="#i18n">Internationalization Considerations</a></li>
    492          <li>7.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
    493          <li>8.&nbsp;&nbsp;&nbsp;<a href="#iana.considerations">IANA Considerations</a><ul>
    494                <li>8.1&nbsp;&nbsp;&nbsp;<a href="#registry">Registry for Disposition Values and Parameter</a></li>
    495                <li>8.2&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
     497         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#examples">Examples</a></li>
     498         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#i18n">Internationalization Considerations</a></li>
     499         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
     500         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#iana.considerations">IANA Considerations</a><ul>
     501               <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#registry">Registry for Disposition Values and Parameter</a></li>
     502               <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
    496503            </ul>
    497504         </li>
    498          <li>9.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9">Acknowledgements</a></li>
    499          <li>10.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
    500                <li>10.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    501                <li>10.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     505         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9">Acknowledgements</a></li>
     506         <li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     507               <li><a href="#rfc.section.10.1">10.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     508               <li><a href="#rfc.section.10.2">10.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    502509            </ul>
    503510         </li>
    504          <li><a href="#rfc.authors">Author's Address</a></li>
    505          <li>A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc2616">Changes from the RFC 2616 Definition</a></li>
    506          <li>B.&nbsp;&nbsp;&nbsp;<a href="#diffs.compared.to.rfc2183">Differences compared to RFC 2183</a></li>
    507          <li>C.&nbsp;&nbsp;&nbsp;<a href="#alternatives">Alternative Approaches to Internationalization</a><ul>
    508                <li>C.1&nbsp;&nbsp;&nbsp;<a href="#alternatives.rfc2047">RFC 2047 Encoding</a></li>
    509                <li>C.2&nbsp;&nbsp;&nbsp;<a href="#alternatives.percent">Percent Encoding</a></li>
    510                <li>C.3&nbsp;&nbsp;&nbsp;<a href="#alternatives.sniff">Encoding Sniffing</a></li>
    511                <li>C.4&nbsp;&nbsp;&nbsp;<a href="#alternatives.implementations">Implementations (to be removed by RFC Editor before publication)</a></li>
     511         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc2616">Changes from the RFC 2616 Definition</a></li>
     512         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#diffs.compared.to.rfc2183">Differences compared to RFC 2183</a></li>
     513         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#alternatives">Alternative Approaches to Internationalization</a><ul>
     514               <li><a href="#rfc.section.C.1">C.1</a>&nbsp;&nbsp;&nbsp;<a href="#alternatives.rfc2047">RFC 2047 Encoding</a></li>
     515               <li><a href="#rfc.section.C.2">C.2</a>&nbsp;&nbsp;&nbsp;<a href="#alternatives.percent">Percent Encoding</a></li>
     516               <li><a href="#rfc.section.C.3">C.3</a>&nbsp;&nbsp;&nbsp;<a href="#alternatives.sniff">Encoding Sniffing</a></li>
     517               <li><a href="#rfc.section.C.4">C.4</a>&nbsp;&nbsp;&nbsp;<a href="#alternatives.implementations">Implementations (to be removed by RFC Editor before publication)</a></li>
    512518            </ul>
    513519         </li>
    514          <li>D.&nbsp;&nbsp;&nbsp;<a href="#advice.generating">Advice on Generating Content-Disposition Header Fields</a></li>
    515          <li>E.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
    516                <li>E.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.1">Since draft-reschke-rfc2183-in-http-00</a></li>
    517                <li>E.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.2">Since draft-reschke-rfc2183-in-http-01</a></li>
    518                <li>E.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.3">Since draft-reschke-rfc2183-in-http-02</a></li>
    519                <li>E.4&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.4">Since draft-reschke-rfc2183-in-http-03</a></li>
    520                <li>E.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.00">Since draft-ietf-httpbis-content-disp-00</a></li>
    521                <li>E.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.01">Since draft-ietf-httpbis-content-disp-01</a></li>
    522                <li>E.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-content-disp-02</a></li>
    523                <li>E.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-content-disp-03</a></li>
    524                <li>E.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-content-disp-04</a></li>
    525                <li>E.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-content-disp-05</a></li>
    526                <li>E.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-content-disp-06</a></li>
    527                <li>E.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-content-disp-07</a></li>
    528                <li>E.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-content-disp-08</a></li>
     520         <li><a href="#rfc.section.D">D.</a>&nbsp;&nbsp;&nbsp;<a href="#advice.generating">Advice on Generating Content-Disposition Header Fields</a></li>
     521         <li><a href="#rfc.section.E">E.</a>&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
     522               <li><a href="#rfc.section.E.1">E.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.1">Since draft-reschke-rfc2183-in-http-00</a></li>
     523               <li><a href="#rfc.section.E.2">E.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.2">Since draft-reschke-rfc2183-in-http-01</a></li>
     524               <li><a href="#rfc.section.E.3">E.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.3">Since draft-reschke-rfc2183-in-http-02</a></li>
     525               <li><a href="#rfc.section.E.4">E.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.4">Since draft-reschke-rfc2183-in-http-03</a></li>
     526               <li><a href="#rfc.section.E.5">E.5</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.00">Since draft-ietf-httpbis-content-disp-00</a></li>
     527               <li><a href="#rfc.section.E.6">E.6</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.01">Since draft-ietf-httpbis-content-disp-01</a></li>
     528               <li><a href="#rfc.section.E.7">E.7</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-content-disp-02</a></li>
     529               <li><a href="#rfc.section.E.8">E.8</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-content-disp-03</a></li>
     530               <li><a href="#rfc.section.E.9">E.9</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-content-disp-04</a></li>
     531               <li><a href="#rfc.section.E.10">E.10</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-content-disp-05</a></li>
     532               <li><a href="#rfc.section.E.11">E.11</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-content-disp-06</a></li>
     533               <li><a href="#rfc.section.E.12">E.12</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-content-disp-07</a></li>
     534               <li><a href="#rfc.section.E.13">E.13</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-content-disp-08</a></li>
    529535            </ul>
    530536         </li>
    531537         <li><a href="#rfc.index">Index</a></li>
     538         <li><a href="#rfc.authors">Author's Address</a></li>
    532539      </ul>
    533       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    534       <p id="rfc.section.1.p.1">RFC 2616 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>):
    535       </p>
    536       <blockquote id="rfc.section.1.p.2" cite="http://tools.ietf.org/html/rfc2616#section-15.5">
    537          <p>Content-Disposition is not part of the HTTP standard, but since it is widely implemented, we are documenting its use and risks
    538             for implementers.
    539          </p>
    540       </blockquote>
    541       <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
    542          testing with existing User Agents, it fully defines a profile of the features defined in the Multipurpose Internet Mail Extensions
    543          (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.
    544       </p>
    545       <div class="note" id="rfc.section.1.p.4">
    546          <p> <b>Note:</b> this document does not apply to Content-Disposition header fields appearing in payload bodies transmitted over HTTP, such
    547             as when using the media type "multipart/form-data" (<a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>).
    548          </p>
    549       </div>
    550       <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="notational.conventions" href="#notational.conventions">Notational Conventions</a></h1>
    551       <p id="rfc.section.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
    552          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>.
    553       </p>
    554       <p id="rfc.section.2.p.2">This specification uses the augmented BNF (ABNF) 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 implied linear whitespace (LWS).
    555       </p>
    556       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="conformance.and.error.handling" href="#conformance.and.error.handling">Conformance and Error Handling</a></h1>
    557       <p id="rfc.section.3.p.1">This specification defines conformance criteria for both senders (usually, HTTP origin servers) and recipients (usually, HTTP
    558          user agents) of the Content-Disposition header field. An implementation is considered conformant if it complies with all of
    559          the requirements associated with its role.
    560       </p>
    561       <p id="rfc.section.3.p.2">This specification also defines certain forms of the header field-value to be invalid, using both ABNF and prose requirements
    562          (<a href="#header.field.definition" id="rfc.xref.header.field.definition.1" title="Header Field Definition">Section&nbsp;4</a>), but it does not define special handling of these invalid field-values.
    563       </p>
    564       <p id="rfc.section.3.p.3">Senders <em class="bcp14">MUST NOT</em> generate Content-Disposition header fields that are invalid.
    565       </p>
    566       <p id="rfc.section.3.p.4">Recipients <em class="bcp14">MAY</em> take steps to recover a usable field-value from an invalid header field, but <em class="bcp14">SHOULD NOT</em> reject the message outright, unless this is explicitly desirable behaviour (e.g., the implementation is a validator). As such,
    567          the default handling of invalid fields is to ignore them.
    568       </p>
    569       <div id="rfc.iref.h.1"></div>
    570       <div id="rfc.iref.c.1"></div>
    571       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="header.field.definition" href="#header.field.definition">Header Field Definition</a></h1>
    572       <p id="rfc.section.4.p.1">The Content-Disposition response header field is used to convey additional information about how to process the response payload,
    573          and also can be used to attach additional metadata, such as the filename to use when saving the response payload locally.
    574       </p>
    575       <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;Grammar
    576       </h2>
    577       <div id="rfc.figure.u.1"></div><pre class="inline">  content-disposition = "Content-Disposition" ":"
     540      <div id="introduction">
     541         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     542         <p id="rfc.section.1.p.1">RFC 2616 defines the Content-Disposition response header field in <a href="https://tools.ietf.org/html/rfc2616#section-19.5.1">Section 19.5.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, but points out that it is not part of the HTTP/1.1 Standard (<a href="https://tools.ietf.org/html/rfc2616#section-15.5" id="rfc.xref.RFC2616.2">Section 15.5</a>):
     543         </p>
     544         <blockquote id="rfc.section.1.p.2" cite="http://tools.ietf.org/html/rfc2616#section-15.5">
     545            <p>Content-Disposition is not part of the HTTP standard, but since it is widely implemented, we are documenting its use and risks
     546               for implementers.
     547            </p>
     548         </blockquote>
     549         <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
     550            testing with existing User Agents, it fully defines a profile of the features defined in the Multipurpose Internet Mail Extensions
     551            (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.
     552         </p>
     553         <div class="note" id="rfc.section.1.p.4">
     554            <p><b>Note:</b> this document does not apply to Content-Disposition header fields appearing in payload bodies transmitted over HTTP, such
     555               as when using the media type "multipart/form-data" (<a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>).
     556            </p>
     557         </div>
     558      </div>
     559      <div id="notational.conventions">
     560         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#notational.conventions">Notational Conventions</a></h1>
     561         <p id="rfc.section.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
     562            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>.
     563         </p>
     564         <p id="rfc.section.2.p.2">This specification uses the augmented BNF (ABNF) notation defined in <a href="https://tools.ietf.org/html/rfc2616#section-2.1">Section 2.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, including its rules for implied linear whitespace (LWS).
     565         </p>
     566      </div>
     567      <div id="conformance.and.error.handling">
     568         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#conformance.and.error.handling">Conformance and Error Handling</a></h1>
     569         <p id="rfc.section.3.p.1">This specification defines conformance criteria for both senders (usually, HTTP origin servers) and recipients (usually, HTTP
     570            user agents) of the Content-Disposition header field. An implementation is considered conformant if it complies with all of
     571            the requirements associated with its role.
     572         </p>
     573         <p id="rfc.section.3.p.2">This specification also defines certain forms of the header field-value to be invalid, using both ABNF and prose requirements
     574            (<a href="#header.field.definition" id="rfc.xref.header.field.definition.1" title="Header Field Definition">Section&nbsp;4</a>), but it does not define special handling of these invalid field-values.
     575         </p>
     576         <p id="rfc.section.3.p.3">Senders <em class="bcp14">MUST NOT</em> generate Content-Disposition header fields that are invalid.
     577         </p>
     578         <p id="rfc.section.3.p.4">Recipients <em class="bcp14">MAY</em> take steps to recover a usable field-value from an invalid header field, but <em class="bcp14">SHOULD NOT</em> reject the message outright, unless this is explicitly desirable behaviour (e.g., the implementation is a validator). As such,
     579            the default handling of invalid fields is to ignore them.
     580         </p>
     581      </div>
     582      <div id="header.field.definition">
     583         <div id="rfc.iref.h.1"></div>
     584         <div id="rfc.iref.c.1"></div>
     585         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#header.field.definition">Header Field Definition</a></h1>
     586         <p id="rfc.section.4.p.1">The Content-Disposition response header field is used to convey additional information about how to process the response payload,
     587            and also can be used to attach additional metadata, such as the filename to use when saving the response payload locally.
     588         </p>
     589         <div>
     590            <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;Grammar
     591            </h2>
     592            <div id="rfc.figure.u.1"></div><pre class="inline">  content-disposition = "Content-Disposition" ":"
    578593                         disposition-type *( ";" disposition-parm )
    579594
     
    590605                      | ext-token "=" ext-value
    591606  ext-token           = &lt;the characters in token, followed by "*"&gt;
    592 </pre><div id="rfc.figure.u.2"></div> 
    593       <p>Defined in <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>:
    594       </p>  <pre class="inline">  token         = &lt;token, defined in <a href="#RFC2616" id="rfc.xref.RFC2616.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>&gt;
    595   quoted-string = &lt;quoted-string, defined in <a href="#RFC2616" id="rfc.xref.RFC2616.6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>&gt;
    596   value         = &lt;value, defined in <a href="#RFC2616" id="rfc.xref.RFC2616.7"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-3.6">Section 3.6</a>&gt;
     607</pre><div id="rfc.figure.u.2"></div>
     608            <p>Defined in <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>:
     609            </p><pre class="inline">  token         = &lt;token, defined in <a href="#RFC2616" id="rfc.xref.RFC2616.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="https://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>&gt;
     610  quoted-string = &lt;quoted-string, defined in <a href="#RFC2616" id="rfc.xref.RFC2616.6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="https://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>&gt;
     611  value         = &lt;value, defined in <a href="#RFC2616" id="rfc.xref.RFC2616.7"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="https://tools.ietf.org/html/rfc2616#section-3.6">Section 3.6</a>&gt;
    597612                ; token | quoted-string
    598613             
    599 </pre><div id="rfc.figure.u.3"></div> 
    600       <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>:
    601       </p>  <pre class="inline">  ext-value   = &lt;ext-value, defined in <a href="#RFC5987" id="rfc.xref.RFC5987.2"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>, <a href="http://tools.ietf.org/html/rfc5987#section-3.2">Section 3.2</a>&gt;
     614</pre><div id="rfc.figure.u.3"></div>
     615            <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>:
     616            </p><pre class="inline">  ext-value   = &lt;ext-value, defined in <a href="#RFC5987" id="rfc.xref.RFC5987.2"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>, <a href="https://tools.ietf.org/html/rfc5987#section-3.2">Section 3.2</a>&gt;
    602617</pre><p id="rfc.section.4.1.p.4">Content-Disposition header field values with multiple instances of the same parameter name are invalid.</p>
    603       <p id="rfc.section.4.1.p.5">Note that due to the rules for implied linear whitespace (<a href="http://tools.ietf.org/html/rfc2616#section-2.1">Section 2.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.8"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>), <em class="bcp14">OPTIONAL</em> whitespace can appear between words (token or quoted-string) and separator characters.
    604       </p>
    605       <p id="rfc.section.4.1.p.6">Furthermore note that the format used for ext-value allows specifying a natural language (e.g., "en"); this is of limited
    606          use for filenames and is likely to be ignored by recipients.
    607       </p>
    608       <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="disposition.type" href="#disposition.type">Disposition Type</a></h2>
    609       <p id="rfc.section.4.2.p.1">If the disposition type matches "attachment" (case-insensitively), this indicates that the recipient should prompt the user
    610          to save the response locally, rather than process it normally (as per its media type).
    611       </p>
    612       <p id="rfc.section.4.2.p.2">On the other hand, if it matches "inline" (case-insensitively), this implies default processing. Therefore, the disposition
    613          type "inline" is only useful when it is augmented with additional parameters, such as the filename (see below).
    614       </p>
    615       <p id="rfc.section.4.2.p.3">Unknown or unhandled disposition types <em class="bcp14">SHOULD</em> be handled by recipients the same way as "attachment" (see also <a href="#RFC2183" id="rfc.xref.RFC2183.2"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>, <a href="http://tools.ietf.org/html/rfc2183#section-2.8">Section 2.8</a>).
    616       </p>
    617       <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a id="disposition.parameter.filename" href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></h2>
    618       <p id="rfc.section.4.3.p.1">The parameters "filename" and "filename*", to be matched case-insensitively, provide information on how to construct a filename
    619          for storing the message payload.
    620       </p>
    621       <p id="rfc.section.4.3.p.2">Depending on the disposition type, this information might be used right away (in the "save as..." interaction caused for the
    622          "attachment" disposition type), or later on (for instance, when the user decides to save the contents of the current page
    623          being displayed).
    624       </p>
    625       <p id="rfc.section.4.3.p.3">The parameters "filename" and "filename*" differ only in that "filename*" uses the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.3"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>, allowing the use of characters not present in the ISO-8859-1 character set (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>).
    626       </p>
    627       <p id="rfc.section.4.3.p.4">Many user agent implementations predating this specification do not understand the "filename*" parameter. Therefore, when
    628          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
    629          more expressive "filename*" parameter, and the "filename" parameter as fallback for legacy recipients (see <a href="#examples" title="Examples">Section&nbsp;5</a> for an example).
    630       </p>
    631       <p id="rfc.section.4.3.p.5">It is essential that recipients treat the specified filename as advisory only, thus be very careful in extracting the desired
    632          information. In particular:
    633       </p>
    634       <ul>
    635          <li>
    636             <p>Recipients <em class="bcp14">MUST NOT</em> be able to write into any location other than one to which they are specifically entitled. To illustrate the problem consider
    637                the consequences of being able to overwrite well-known system locations (such as "/etc/passwd"). One strategy to achieve this
    638                is to never trust folder name information in the filename parameter, for instance by stripping all but the last path segment
    639                and only consider the actual filename (where 'path segment' are the components of the field value delimited by the path separator
    640                characters "\" and "/").
    641             </p>
    642          </li>
    643          <li>
    644             <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
    645                extension could introduce a privilege escalation when the saved file is later opened (consider ".exe"). Thus, recipients which
    646                make use of file extensions to determine the media type <em class="bcp14">MUST</em> ensure that a file extension is used that is safe, optimally matching the media type of the received payload.
    647             </p>
    648          </li>
    649          <li>
    650             <p>Recipients <em class="bcp14">SHOULD</em> strip or replace character sequences that are known to cause confusion both in user interfaces and in filenames, such as control
    651                characters and leading and trailing whitespace.
    652             </p>
    653          </li>
    654          <li>
    655             <p>Other aspects recipients need to be aware of are names that have a special meaning in the file system or in shell commands,
    656                such as "." and "..", "~", "|", and also device names. Recipients <em class="bcp14">SHOULD</em> ignore or substitute names like these.
    657             </p>
    658          </li>
    659       </ul>
    660       <div class="note" id="rfc.section.4.3.p.6">
    661          <p> <b>Note:</b> Many user agents do not properly handle the escape character "\" when using the quoted-string form. Furthermore, some user
    662             agents erroneously try to perform unescaping of "percent" escapes (see <a href="#alternatives.percent" title="Percent Encoding">Appendix&nbsp;C.2</a>), and thus might misinterpret filenames containing the percent character followed by two hex digits.
    663          </p>
    664       </div>
    665       <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a id="disposition.parameter.extensions" href="#disposition.parameter.extensions">Disposition Parameter: Extensions</a></h2>
    666       <p id="rfc.section.4.4.p.1">To enable future extensions, recipients <em class="bcp14">SHOULD</em> ignore unrecognized parameters (see also <a href="#RFC2183" id="rfc.xref.RFC2183.3"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>, <a href="http://tools.ietf.org/html/rfc2183#section-2.8">Section 2.8</a>).
    667       </p>
    668       <h2 id="rfc.section.4.5"><a href="#rfc.section.4.5">4.5</a>&nbsp;<a id="extensibility" href="#extensibility">Extensibility</a></h2>
    669       <p id="rfc.section.4.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
    670          using Content-Disposition, such as MIME and HTTP. Therefore, not all registered values may make sense in the context of HTTP.
    671       </p>
    672       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="examples" href="#examples">Examples</a></h1>
    673       <div id="rfc.figure.u.4"></div>
    674       <p>Direct UA to show "save as" dialog, with a filename of "example.html":</p>  <pre class="text">Content-Disposition: Attachment; filename=example.html
    675 </pre><div id="rfc.figure.u.5"></div>
    676       <p>Direct UA to behave as if the Content-Disposition header field wasn't present, but to remember the filename "an example.html"
    677          for a subsequent save operation:
    678       </p>  <pre class="text">Content-Disposition: INLINE; FILENAME= "an example.html"
    679 </pre>  <p>Note: this uses the quoted-string form so that the space character can be included.</p>
    680       <div id="rfc.figure.u.6"></div>
    681       <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;
     618            <p id="rfc.section.4.1.p.5">Note that due to the rules for implied linear whitespace (<a href="https://tools.ietf.org/html/rfc2616#section-2.1">Section 2.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.8"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>), <em class="bcp14">OPTIONAL</em> whitespace can appear between words (token or quoted-string) and separator characters.
     619            </p>
     620            <p id="rfc.section.4.1.p.6">Furthermore note that the format used for ext-value allows specifying a natural language (e.g., "en"); this is of limited
     621               use for filenames and is likely to be ignored by recipients.
     622            </p>
     623         </div>
     624         <div id="disposition.type">
     625            <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#disposition.type">Disposition Type</a></h2>
     626            <p id="rfc.section.4.2.p.1">If the disposition type matches "attachment" (case-insensitively), this indicates that the recipient should prompt the user
     627               to save the response locally, rather than process it normally (as per its media type).
     628            </p>
     629            <p id="rfc.section.4.2.p.2">On the other hand, if it matches "inline" (case-insensitively), this implies default processing. Therefore, the disposition
     630               type "inline" is only useful when it is augmented with additional parameters, such as the filename (see below).
     631            </p>
     632            <p id="rfc.section.4.2.p.3">Unknown or unhandled disposition types <em class="bcp14">SHOULD</em> be handled by recipients the same way as "attachment" (see also <a href="#RFC2183" id="rfc.xref.RFC2183.2"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>, <a href="https://tools.ietf.org/html/rfc2183#section-2.8">Section 2.8</a>).
     633            </p>
     634         </div>
     635         <div id="disposition.parameter.filename">
     636            <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></h2>
     637            <p id="rfc.section.4.3.p.1">The parameters "filename" and "filename*", to be matched case-insensitively, provide information on how to construct a filename
     638               for storing the message payload.
     639            </p>
     640            <p id="rfc.section.4.3.p.2">Depending on the disposition type, this information might be used right away (in the "save as..." interaction caused for the
     641               "attachment" disposition type), or later on (for instance, when the user decides to save the contents of the current page
     642               being displayed).
     643            </p>
     644            <p id="rfc.section.4.3.p.3">The parameters "filename" and "filename*" differ only in that "filename*" uses the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.3"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>, allowing the use of characters not present in the ISO-8859-1 character set (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>).
     645            </p>
     646            <p id="rfc.section.4.3.p.4">Many user agent implementations predating this specification do not understand the "filename*" parameter. Therefore, when
     647               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
     648               more expressive "filename*" parameter, and the "filename" parameter as fallback for legacy recipients (see <a href="#examples" title="Examples">Section&nbsp;5</a> for an example).
     649            </p>
     650            <p id="rfc.section.4.3.p.5">It is essential that recipients treat the specified filename as advisory only, thus be very careful in extracting the desired
     651               information. In particular:
     652            </p>
     653            <ul>
     654               <li>
     655                  <p>Recipients <em class="bcp14">MUST NOT</em> be able to write into any location other than one to which they are specifically entitled. To illustrate the problem consider
     656                     the consequences of being able to overwrite well-known system locations (such as "/etc/passwd"). One strategy to achieve this
     657                     is to never trust folder name information in the filename parameter, for instance by stripping all but the last path segment
     658                     and only consider the actual filename (where 'path segment' are the components of the field value delimited by the path separator
     659                     characters "\" and "/").
     660                  </p>
     661               </li>
     662               <li>
     663                  <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
     664                     extension could introduce a privilege escalation when the saved file is later opened (consider ".exe"). Thus, recipients which
     665                     make use of file extensions to determine the media type <em class="bcp14">MUST</em> ensure that a file extension is used that is safe, optimally matching the media type of the received payload.
     666                  </p>
     667               </li>
     668               <li>
     669                  <p>Recipients <em class="bcp14">SHOULD</em> strip or replace character sequences that are known to cause confusion both in user interfaces and in filenames, such as control
     670                     characters and leading and trailing whitespace.
     671                  </p>
     672               </li>
     673               <li>
     674                  <p>Other aspects recipients need to be aware of are names that have a special meaning in the file system or in shell commands,
     675                     such as "." and "..", "~", "|", and also device names. Recipients <em class="bcp14">SHOULD</em> ignore or substitute names like these.
     676                  </p>
     677               </li>
     678            </ul>
     679            <div class="note" id="rfc.section.4.3.p.6">
     680               <p><b>Note:</b> Many user agents do not properly handle the escape character "\" when using the quoted-string form. Furthermore, some user
     681                  agents erroneously try to perform unescaping of "percent" escapes (see <a href="#alternatives.percent" title="Percent Encoding">Appendix&nbsp;C.2</a>), and thus might misinterpret filenames containing the percent character followed by two hex digits.
     682               </p>
     683            </div>
     684         </div>
     685         <div id="disposition.parameter.extensions">
     686            <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a href="#disposition.parameter.extensions">Disposition Parameter: Extensions</a></h2>
     687            <p id="rfc.section.4.4.p.1">To enable future extensions, recipients <em class="bcp14">SHOULD</em> ignore unrecognized parameters (see also <a href="#RFC2183" id="rfc.xref.RFC2183.3"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>, <a href="https://tools.ietf.org/html/rfc2183#section-2.8">Section 2.8</a>).
     688            </p>
     689         </div>
     690         <div id="extensibility">
     691            <h2 id="rfc.section.4.5"><a href="#rfc.section.4.5">4.5</a>&nbsp;<a href="#extensibility">Extensibility</a></h2>
     692            <p id="rfc.section.4.5.p.1">Note that <a href="https://tools.ietf.org/html/rfc2183#section-9">Section 9</a> of <a href="#RFC2183" id="rfc.xref.RFC2183.4"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a> defines IANA registries both for disposition types and disposition parameters. This registry is shared by different protocols
     693               using Content-Disposition, such as MIME and HTTP. Therefore, not all registered values may make sense in the context of HTTP.
     694            </p>
     695         </div>
     696      </div>
     697      <div id="examples">
     698         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#examples">Examples</a></h1>
     699         <div id="rfc.figure.u.4"></div>
     700         <p>Direct UA to show "save as" dialog, with a filename of "example.html":</p><pre class="text">Content-Disposition: Attachment; filename=example.html
     701</pre><div id="rfc.figure.u.5"></div>
     702         <p>Direct UA to behave as if the Content-Disposition header field wasn't present, but to remember the filename "an example.html"
     703            for a subsequent save operation:
     704         </p><pre class="text">Content-Disposition: INLINE; FILENAME= "an example.html"
     705</pre><p>Note: this uses the quoted-string form so that the space character can be included.</p>
     706         <div id="rfc.figure.u.6"></div>
     707         <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;
    682708                     filename*= UTF-8''<b>%e2%82%ac</b>%20rates
    683 </pre>  <p>Here, the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.4"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a> is also used to encode the non-ISO-8859-1 character.
    684       </p>
    685       <div id="rfc.figure.u.7"></div>
    686       <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;
     709</pre><p>Here, the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.4"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a> is also used to encode the non-ISO-8859-1 character.
     710         </p>
     711         <div id="rfc.figure.u.7"></div>
     712         <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;
    687713                     filename="EURO rates";
    688714                     filename*=utf-8''<b>%e2%82%ac</b>%20rates
    689 </pre>  <p>Note: those user agents that do not support the RFC 5987 encoding ignore "filename*" when it occurs after "filename".</p>
    690       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="i18n" href="#i18n">Internationalization Considerations</a></h1>
    691       <p id="rfc.section.6.p.1">The "filename*" parameter (<a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;4.3</a>), using the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.5"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>, allows the server to transmit characters outside the ISO-8859-1 character set, and also to optionally specify the language
    692          in use.
    693       </p>
    694       <p id="rfc.section.6.p.2">Future parameters might also require internationalization, in which case the same encoding can be used.</p>
    695       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    696       <p id="rfc.section.7.p.1">Using server-supplied information for constructing local filenames introduces many risks. These are summarized in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;4.3</a>.
    697       </p>
    698       <p id="rfc.section.7.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.9"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>), and also the parameter encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.6"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a> (see <a href="http://tools.ietf.org/html/rfc5987#section-5" id="rfc.xref.RFC5987.7">Section 5</a>).
    699       </p>
    700       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="iana.considerations" href="#iana.considerations">IANA Considerations</a></h1>
    701       <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="registry" href="#registry">Registry for Disposition Values and Parameter</a></h2>
    702       <p id="rfc.section.8.1.p.1">This specification does not introduce any changes to the registration procedures for disposition values and parameters that
    703          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>.
    704       </p>
    705       <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
    706       <p id="rfc.section.8.2.p.1">This document updates the definition of the Content-Disposition HTTP header field in the permanent HTTP header field registry
    707          (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>).
    708       </p>
    709       <p id="rfc.section.8.2.p.2"> </p>
    710       <dl>
    711          <dt>Header field name:</dt>
    712          <dd>Content-Disposition</dd>
    713          <dt>Applicable protocol:</dt>
    714          <dd>http</dd>
    715          <dt>Status:</dt>
    716          <dd>standard</dd>
    717          <dt>Author/Change controller:</dt>
    718          <dd>IETF</dd>
    719          <dt>Specification document:</dt>
    720          <dd>this specification (<a href="#header.field.definition" id="rfc.xref.header.field.definition.2" title="Header Field Definition">Section&nbsp;4</a>)
    721          </dd>
    722          <dt>Related information:</dt>
    723          <dd>none</dd>
    724       </dl>
    725       <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;Acknowledgements
    726       </h1>
    727       <p id="rfc.section.9.p.1">Thanks to Adam Barth, Rolf Eike Beer, Stewart Bryant, Bjoern Hoehrmann, Alfred Hoenes, Roar Lauritzsen, Alexey Melnikov, Henrik
    728          Nordstrom, and Mark Nottingham for their valuable feedback.
    729       </p>
     715</pre><p>Note: those user agents that do not support the RFC 5987 encoding ignore "filename*" when it occurs after "filename".</p>
     716      </div>
     717      <div id="i18n">
     718         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#i18n">Internationalization Considerations</a></h1>
     719         <p id="rfc.section.6.p.1">The "filename*" parameter (<a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;4.3</a>), using the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.5"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>, allows the server to transmit characters outside the ISO-8859-1 character set, and also to optionally specify the language
     720            in use.
     721         </p>
     722         <p id="rfc.section.6.p.2">Future parameters might also require internationalization, in which case the same encoding can be used.</p>
     723      </div>
     724      <div id="security.considerations">
     725         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     726         <p id="rfc.section.7.p.1">Using server-supplied information for constructing local filenames introduces many risks. These are summarized in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;4.3</a>.
     727         </p>
     728         <p id="rfc.section.7.p.2">Furthermore, implementers also ought to be aware of the Security Considerations applying to HTTP (see <a href="https://tools.ietf.org/html/rfc2616#section-15">Section 15</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.9"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>), and also the parameter encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.6"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a> (see <a href="https://tools.ietf.org/html/rfc5987#section-5" id="rfc.xref.RFC5987.7">Section 5</a>).
     729         </p>
     730      </div>
     731      <div id="iana.considerations">
     732         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#iana.considerations">IANA Considerations</a></h1>
     733         <div id="registry">
     734            <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a href="#registry">Registry for Disposition Values and Parameter</a></h2>
     735            <p id="rfc.section.8.1.p.1">This specification does not introduce any changes to the registration procedures for disposition values and parameters that
     736               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>.
     737            </p>
     738         </div>
     739         <div id="header.field.registration">
     740            <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
     741            <p id="rfc.section.8.2.p.1">This document updates the definition of the Content-Disposition HTTP header field in the permanent HTTP header field registry
     742               (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>).
     743            </p>
     744            <p id="rfc.section.8.2.p.2"></p>
     745            <dl>
     746               <dt>Header field name:</dt>
     747               <dd>Content-Disposition</dd>
     748               <dt>Applicable protocol:</dt>
     749               <dd>http</dd>
     750               <dt>Status:</dt>
     751               <dd>standard</dd>
     752               <dt>Author/Change controller:</dt>
     753               <dd>IETF</dd>
     754               <dt>Specification document:</dt>
     755               <dd>this specification (<a href="#header.field.definition" id="rfc.xref.header.field.definition.2" title="Header Field Definition">Section&nbsp;4</a>)
     756               </dd>
     757               <dt>Related information:</dt>
     758               <dd>none</dd>
     759            </dl>
     760         </div>
     761      </div>
     762      <div>
     763         <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;Acknowledgements
     764         </h1>
     765         <p id="rfc.section.9.p.1">Thanks to Adam Barth, Rolf Eike Beer, Stewart Bryant, Bjoern Hoehrmann, Alfred Hoenes, Roar Lauritzsen, Alexey Melnikov, Henrik
     766            Nordstrom, and Mark Nottingham for their valuable feedback.
     767         </p>
     768      </div>
    730769      <h1 id="rfc.references"><a id="rfc.section.10" href="#rfc.section.10">10.</a> References
    731770      </h1>
    732771      <h2 id="rfc.references.1"><a href="#rfc.section.10.1" id="rfc.section.10.1">10.1</a> Normative References
    733772      </h2>
    734       <table>       
     773      <table>
    735774         <tr>
    736775            <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td>
     
    739778         <tr>
    740779            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    741             <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&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
     780            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
    742781            </td>
    743782         </tr>
    744783         <tr>
    745784            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    746             <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&nbsp;2616, June&nbsp;1999.
     785            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
    747786            </td>
    748787         </tr>
    749788         <tr>
    750789            <td class="reference"><b id="RFC5987">[RFC5987]</b></td>
    751             <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&nbsp;5987, August&nbsp;2010.
     790            <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="https://tools.ietf.org/html/rfc5987">Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters</a>”, RFC&nbsp;5987, August&nbsp;2010.
    752791            </td>
    753792         </tr>
     
    755794      <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References
    756795      </h2>
    757       <table>                 
     796      <table>
    758797         <tr>
    759798            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
    760             <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&nbsp;2046, November&nbsp;1996.
     799            <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="https://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC&nbsp;2046, November&nbsp;1996.
    761800            </td>
    762801         </tr>
    763802         <tr>
    764803            <td class="reference"><b id="RFC2047">[RFC2047]</b></td>
    765             <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&nbsp;2047, November&nbsp;1996.
     804            <td class="top"><a href="mailto:moore@cs.utk.edu" title="University of Tennessee">Moore, K.</a>, “<a href="https://tools.ietf.org/html/rfc2047">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</a>”, RFC&nbsp;2047, November&nbsp;1996.
    766805            </td>
    767806         </tr>
    768807         <tr>
    769808            <td class="reference"><b id="RFC2183">[RFC2183]</b></td>
    770             <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&nbsp;2183, August&nbsp;1997.
     809            <td class="top"><a href="mailto:rens@century.com" title="New Century Systems">Troost, R.</a>, <a href="mailto:sdorner@qualcomm.com" title="QUALCOMM Incorporated">Dorner, S.</a>, and <a href="mailto:moore@cs.utk.edu" title="Department of Computer Science">K. Moore</a>, “<a href="https://tools.ietf.org/html/rfc2183">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</a>”, RFC&nbsp;2183, August&nbsp;1997.
    771810            </td>
    772811         </tr>
    773812         <tr>
    774813            <td class="reference"><b id="RFC2231">[RFC2231]</b></td>
    775             <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&nbsp;2231, November&nbsp;1997.
     814            <td class="top"><a href="mailto:ned.freed@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:moore@cs.utk.edu" title="University of Tennessee">K. Moore</a>, “<a href="https://tools.ietf.org/html/rfc2231">MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations</a>”, RFC&nbsp;2231, November&nbsp;1997.
    776815            </td>
    777816         </tr>
    778817         <tr>
    779818            <td class="reference"><b id="RFC2388">[RFC2388]</b></td>
    780             <td class="top"><a href="mailto:masinter@parc.xerox.com" title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2388">Returning Values from Forms: multipart/form-data</a>”, RFC&nbsp;2388, August&nbsp;1998.
     819            <td class="top"><a href="mailto:masinter@parc.xerox.com" title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="https://tools.ietf.org/html/rfc2388">Returning Values from Forms: multipart/form-data</a>”, RFC&nbsp;2388, August&nbsp;1998.
    781820            </td>
    782821         </tr>
    783822         <tr>
    784823            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
    785             <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&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
     824            <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
    786825            </td>
    787826         </tr>
    788827         <tr>
    789828            <td class="reference"><b id="RFC3986">[RFC3986]</b></td>
    790             <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&nbsp;66, RFC&nbsp;3986, January&nbsp;2005.
     829            <td class="top"><a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R.</a>, and <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">L. Masinter</a>, “<a href="https://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, STD&nbsp;66, RFC&nbsp;3986, January&nbsp;2005.
    791830            </td>
    792831         </tr>
     
    796835         </tr>
    797836      </table>
    798       <div class="avoidbreak">
    799          <h1 id="rfc.authors"><a href="#rfc.authors">Author's Address</a></h1>
    800          <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span><span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline">Email: <a href="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>
    801       </div>
    802       <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="changes.from.rfc2616" href="#changes.from.rfc2616">Changes from the RFC 2616 Definition</a></h1>
    803       <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.10"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, the following normative changes reflecting actual implementations have been made:
    804       </p>
    805       <ul>
    806          <li>According to RFC 2616, the disposition type "attachment" only applies to content of type "application/octet-stream". This
    807             restriction has been removed, because recipients in practice do not check the content type, and it also discourages properly
    808             declaring the media type.
    809          </li>
    810          <li>RFC 2616 only allows "quoted-string" for the filename parameter. This would be an exceptional parameter syntax, and also doesn't
    811             reflect actual use.
    812          </li>
    813          <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.
    814          </li>
    815          <li>This specification requires support for the extended parameter encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.8"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>.
    816          </li>
    817       </ul>
    818       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="diffs.compared.to.rfc2183" href="#diffs.compared.to.rfc2183">Differences compared to RFC 2183</a></h1>
    819       <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". The
    820          majority of user agents does not implement these, thus they have been omitted from this specification.
    821       </p>
    822       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="alternatives" href="#alternatives">Alternative Approaches to Internationalization</a></h1>
    823       <p id="rfc.section.C.p.1">By default, HTTP header field parameters cannot carry characters outside the ISO-8859-1 (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.2"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>) character encoding (see <a href="#RFC2616" id="rfc.xref.RFC2616.11"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>). For the "filename" parameter, this of course is an unacceptable restriction.
    824       </p>
    825       <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
    826          Track specifies exactly one solution (<a href="#RFC2231" id="rfc.xref.RFC2231.1"><cite title="MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations">[RFC2231]</cite></a>, clarified and profiled for HTTP in <a href="#RFC5987" id="rfc.xref.RFC5987.9"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>).
    827       </p>
    828       <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
    829          to the RFC 5987 encoding used in this specification.
    830       </p>
    831       <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;<a id="alternatives.rfc2047" href="#alternatives.rfc2047">RFC 2047 Encoding</a></h2>
    832       <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
    833          - 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>:
    834       </p>
    835       <blockquote id="rfc.section.C.1.p.2" cite="http://tools.ietf.org/html/rfc2047#section-5">
    836          <p>An 'encoded-word' MUST NOT appear within a 'quoted-string'.</p> 
    837          <p>...</p> 
    838          <p>An 'encoded-word' MUST NOT be used in parameter of a MIME Content-Type or Content-Disposition field, or in any structured
    839             field body except within a 'comment' or 'phrase'.
    840          </p>
    841       </blockquote>
    842       <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
    843          confused by it.
    844       </p>
    845       <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;<a id="alternatives.percent" href="#alternatives.percent">Percent Encoding</a></h2>
    846       <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. The character encoding being used for decoding depends on various factors, including the encoding
    847          of the referring page, the user agent's locale, its configuration, and also the actual value of the parameter.
    848       </p>
    849       <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
    850          to the user. For those user agents that do implement this it is difficult to predict what character encoding they actually
    851          expect.
    852       </p>
    853       <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;<a id="alternatives.sniff" href="#alternatives.sniff">Encoding Sniffing</a></h2>
    854       <p id="rfc.section.C.3.p.1">Some user agents inspect the value (which defaults to ISO-8859-1 for the quoted-string form) and switch to UTF-8 when it seems
    855          to be more likely to be the correct interpretation.
    856       </p>
    857       <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>
    858       <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a id="alternatives.implementations" href="#alternatives.implementations">Implementations (to be removed by RFC Editor before publication)</a></h2>
    859       <p id="rfc.section.C.4.p.1">Unfortunately, as of March 2011, neither the encoding defined in RFCs 2231 and 5987, nor any of the alternate approaches discussed
    860          above was implemented interoperably. Thus, this specification recommends the approach defined in RFC 5987, which at least
    861          has the advantage of actually being specified properly.
    862       </p>
    863       <p id="rfc.section.C.4.p.2">The table below shows the support for the various approaches in the current implementations:</p>
    864       <div id="rfc.table.u.1">
    865          <table class="tt full left" cellpadding="3" cellspacing="0">
    866             <thead>
    867                <tr>
    868                   <th>User Agent</th>
    869                   <th>RFC 2231/5987</th>
    870                   <th>RFC 2047</th>
    871                   <th>Percent Encoding</th>
    872                   <th>Encoding Sniffing</th>
    873                </tr>
    874             </thead>
    875             <tbody>
    876                <tr>
    877                   <td class="left">Chrome</td>
    878                   <td class="left">yes</td>
    879                   <td class="left">yes</td>
    880                   <td class="left">yes</td>
    881                   <td class="left">yes</td>
    882                </tr>
    883                <tr>
    884                   <td class="left">Firefox</td>
    885                   <td class="left">yes (*)</td>
    886                   <td class="left">yes</td>
    887                   <td class="left">no</td>
    888                   <td class="left">yes</td>
    889                </tr>
    890                <tr>
    891                   <td class="left">Internet Explorer</td>
    892                   <td class="left">yes (**)</td>
    893                   <td class="left">no</td>
    894                   <td class="left">yes</td>
    895                   <td class="left">no</td>
    896                </tr>
    897                <tr>
    898                   <td class="left">Konqueror</td>
    899                   <td class="left">yes</td>
    900                   <td class="left">no</td>
    901                   <td class="left">no</td>
    902                   <td class="left">no</td>
    903                </tr>
    904                <tr>
    905                   <td class="left">Opera</td>
    906                   <td class="left">yes</td>
    907                   <td class="left">no</td>
    908                   <td class="left">no</td>
    909                   <td class="left">no</td>
    910                </tr>
    911                <tr>
    912                   <td class="left">Safari</td>
    913                   <td class="left">no</td>
    914                   <td class="left">no</td>
    915                   <td class="left">no</td>
    916                   <td class="left">yes</td>
    917                </tr>
    918             </tbody>
    919          </table>
    920       </div>
    921       <p id="rfc.section.C.4.p.3">(*) Does not implement the fallback behavior to "filename" described in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;4.3</a>; a fix is planned for Firefox 5.
    922       </p>
    923       <p id="rfc.section.C.4.p.4">(**) Starting with Internet Explorer 9, but only implements UTF-8.</p>
    924       <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="advice.generating" href="#advice.generating">Advice on Generating Content-Disposition Header Fields</a></h1>
    925       <p id="rfc.section.D.p.1">To successfully interoperate with existing and future user agents, senders of the Content-Disposition header field are advised
    926          to:
    927       </p>
    928       <p id="rfc.section.D.p.2"> </p>
    929       <ul>
    930          <li>Include a "filename" parameter when US-ASCII (<a href="#US-ASCII" id="rfc.xref.US-ASCII.1"><cite title="Coded Character Set -- 7-bit American Standard Code for Information Interchange">[US-ASCII]</cite></a>) is sufficiently expressive.
    931          </li>
    932          <li>Use the 'token' form of the filename parameter only when it does not contain disallowed characters (e.g., spaces); in such
    933             cases, the quoted-string form should be used.
    934          </li>
    935          <li>Avoid including the percent character followed by two hexadecimal characters (e.g., %A9) in the filename parameter, since
    936             some existing implementations consider it to be an escape character, while others will pass it through unchanged.
    937          </li>
    938          <li>Avoid including the "\" character in the quoted-string form of the filename parameter, as escaping is not implemented by some
    939             user agents, and can be considered as an illegal path character.
    940          </li>
    941          <li>Avoid using non-ASCII characters in the filename parameter. Although most existing implementations will decode them as ISO-8859-1,
    942             some will apply heuristics to detect UTF-8, and thus might fail on certain names.
    943          </li>
    944          <li>Include a "filename*" parameter where the desired filename cannot be expressed faithfully using the "filename" form. Note
    945             that legacy user agents will not process this, and will fall back to using the "filename" parameter's content.
    946          </li>
    947          <li>When a "filename*" parameter is sent, to also generate a "filename" parameter as a fallback for user agents that do not support
    948             the "filename*" form, if possible. This can be done by substituting characters with US-ASCII sequences (e.g., Unicode character
    949             point U+00E4 (LATIN SMALL LETTER A WITH DIARESIS) by "ae"). Note that this may not be possible in some locales.
    950          </li>
    951          <li>When a "filename" parameter is included as a fallback (as per above), "filename" should occur first, due to parsing problems
    952             in some existing implementations. <span class="comment" id="fallbackbug">[<a href="#fallbackbug" class="smpl">fallbackbug</a>: Firefox is known to pick the wrong parameter; a bug fix is scheduled for Firefox 5. --jre]</span>  <span class="comment" id="NOTE-TO-RFC-EDITOR">[<a href="#NOTE-TO-RFC-EDITOR" class="smpl">NOTE-TO-RFC-EDITOR</a>: PLEASE REMOVE THIS AND THE PRECEDING COMMENT BEFORE PUBLICATION AS RFC. --jre]</span>
    953          </li>
    954          <li>Use UTF-8 as the encoding of the "filename*" parameter, when present, because at least one existing implementation only implements
    955             that encoding.
    956          </li>
    957       </ul>
    958       <p id="rfc.section.D.p.3">Note that this advice is based upon UA behaviour at the time of writing, and might be superseded. At the time of publication
    959          of this document, &lt;<a href="http://purl.org/NET/http/content-disposition-tests">http://purl.org/NET/http/content-disposition-tests</a>&gt; provides an overview of current levels of support in various implementations.
    960       </p>
    961       <h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    962       <p id="rfc.section.E.p.1">Note: the issues names in the change log entries for draft-reschke-rfc2183-in-http refer to &lt;<a href="http://greenbytes.de/tech/webdav/draft-reschke-rfc2183-in-http-issues.html">http://greenbytes.de/tech/webdav/draft-reschke-rfc2183-in-http-issues.html</a>&gt;.
    963       </p>
    964       <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;Since draft-reschke-rfc2183-in-http-00
    965       </h2>
    966       <p id="rfc.section.E.1.p.1">Adjust terminology ("header" -&gt; "header field"). Update rfc2231-in-http reference.</p>
    967       <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;Since draft-reschke-rfc2183-in-http-01
    968       </h2>
    969       <p id="rfc.section.E.2.p.1">Update rfc2231-in-http reference. Actually define the "filename" parameter. Add internationalization considerations. Add examples
    970          using the RFC 5987 encoding. Add overview over other approaches, plus a table reporting implementation status. Add and resolve
    971          issue "nodep2183". Add issues "asciivsiso", "deplboth", "quoted", and "registry".
    972       </p>
    973       <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a>&nbsp;Since draft-reschke-rfc2183-in-http-02
    974       </h2>
    975       <p id="rfc.section.E.3.p.1">Add and close issue "docfallback". Close issues "asciivsiso", "deplboth", "quoted", and "registry".</p>
    976       <h2 id="rfc.section.E.4"><a href="#rfc.section.E.4">E.4</a>&nbsp;Since draft-reschke-rfc2183-in-http-03
    977       </h2>
    978       <p id="rfc.section.E.4.p.1">Updated to be a Working Draft of the IETF HTTPbis Working Group.</p>
    979       <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;<a id="changes.since.00" href="#changes.since.00">Since draft-ietf-httpbis-content-disp-00</a></h2>
    980       <p id="rfc.section.E.5.p.1">Closed issues: </p>
    981       <ul>
    982          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/242">http://tools.ietf.org/wg/httpbis/trac/ticket/242</a>&gt;: "handling of unknown disposition types"
    983          </li>
    984       </ul>
    985       <p id="rfc.section.E.5.p.2">Slightly updated the notes about the proposed fallback behavior.</p>
    986       <h2 id="rfc.section.E.6"><a href="#rfc.section.E.6">E.6</a>&nbsp;<a id="changes.since.01" href="#changes.since.01">Since draft-ietf-httpbis-content-disp-01</a></h2>
    987       <p id="rfc.section.E.6.p.1">Various editorial improvements.</p>
    988       <h2 id="rfc.section.E.7"><a href="#rfc.section.E.7">E.7</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-content-disp-02</a></h2>
    989       <p id="rfc.section.E.7.p.1">Closed issues: </p>
    990       <ul>
    991          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/244">http://tools.ietf.org/wg/httpbis/trac/ticket/244</a>&gt;: "state that repeating parameters are invalid"
    992          </li>
    993          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/245">http://tools.ietf.org/wg/httpbis/trac/ticket/245</a>&gt;: "warn about %xx in filenames being misinterpreted"
    994          </li>
    995          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/246">http://tools.ietf.org/wg/httpbis/trac/ticket/246</a>&gt;: "mention control chars when talking about postprecessing the filename parameter"
    996          </li>
    997       </ul>
    998       <p id="rfc.section.E.7.p.2">Update <a href="#alternatives.implementations" title="Implementations (to be removed by RFC Editor before publication)">Appendix&nbsp;C.4</a>; Opera 10.63 RC implements the recommended fallback behavior.
    999       </p>
    1000       <h2 id="rfc.section.E.8"><a href="#rfc.section.E.8">E.8</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-content-disp-03</a></h2>
    1001       <p id="rfc.section.E.8.p.1">Closed issues: </p>
    1002       <ul>
    1003          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/252">http://tools.ietf.org/wg/httpbis/trac/ticket/252</a>&gt;: "'modification-date' *is* implemented in Konq 4.5"
    1004          </li>
    1005          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/253">http://tools.ietf.org/wg/httpbis/trac/ticket/253</a>&gt;: "clarify what LWS means for the Content-Disp grammar"
    1006          </li>
    1007          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/258">http://tools.ietf.org/wg/httpbis/trac/ticket/258</a>&gt;: "Avoid passive voice in message requirements"
    1008          </li>
    1009          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/263">http://tools.ietf.org/wg/httpbis/trac/ticket/263</a>&gt;: "text about historical percent-decoding unclear"
    1010          </li>
    1011          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/264">http://tools.ietf.org/wg/httpbis/trac/ticket/264</a>&gt;: "add explanation of language tagging"
    1012          </li>
    1013          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/265">http://tools.ietf.org/wg/httpbis/trac/ticket/265</a>&gt;: "Clarify that C-D spec does not apply to multipart upload"
    1014          </li>
    1015       </ul>
    1016       <h2 id="rfc.section.E.9"><a href="#rfc.section.E.9">E.9</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-content-disp-04</a></h2>
    1017       <p id="rfc.section.E.9.p.1">Updated implementation information (Chrome 9 implements RFC 5987, IE 9 RC implements it for UTF-8 only).</p>
    1018       <p id="rfc.section.E.9.p.2">Clarify who requirements are on, add a section discussing conformance and handling of invalid field values in general.</p>
    1019       <p id="rfc.section.E.9.p.3">Closed issues: </p>
    1020       <ul>
    1021          <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/243">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/243</a>&gt;: "avoid stating ISO-8859-1 default for header param" (the default is still mentioned, but it was clarified what it applies
    1022             to).
    1023          </li>
    1024          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/272">http://tools.ietf.org/wg/httpbis/trac/ticket/272</a>&gt;: "Path Separator Characters"
    1025          </li>
    1026       </ul>
    1027       <h2 id="rfc.section.E.10"><a href="#rfc.section.E.10">E.10</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-content-disp-05</a></h2>
    1028       <p id="rfc.section.E.10.p.1">Editorial changes: Fixed two typos where the new Conformance section said "Content-Location" instead of "Content-Disposition".
    1029          Cleaned up terminology ("user agent", "recipient", "sender", "message body", ...). Stated what the escape character for quoted-string
    1030          is. Explained a use case for "inline" disposition type. Updated implementation notes with respect to the fallback behavior.
    1031       </p>
    1032       <p id="rfc.section.E.10.p.2">Added appendix "Advice on Generating Content-Disposition Header Fields".</p>
    1033       <h2 id="rfc.section.E.11"><a href="#rfc.section.E.11">E.11</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-content-disp-06</a></h2>
    1034       <p id="rfc.section.E.11.p.1">Closed issues: </p>
    1035       <ul>
    1036          <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/278">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/278</a>&gt;: "conformance language"
    1037          </li>
    1038       </ul>
    1039       <h2 id="rfc.section.E.12"><a href="#rfc.section.E.12">E.12</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-content-disp-07</a></h2>
    1040       <p id="rfc.section.E.12.p.1">Rephrase the requirement about well-known file system locations, and also clarify that by "last path segment" we mean the
    1041          actual filename. Added a forward reference from "invalid" to the section that defines a valid header field.
    1042       </p>
    1043       <h2 id="rfc.section.E.13"><a href="#rfc.section.E.13">E.13</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-content-disp-08</a></h2>
    1044       <p id="rfc.section.E.13.p.1">Update: Internet Explorer 9 is released. Various editorial improvements. Add US-ASCII reference. Strengthen file extension
    1045          handling requirement to MUST for those recipients that actually use file extensions to map media types.
    1046       </p>
     837      <div id="changes.from.rfc2616">
     838         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#changes.from.rfc2616">Changes from the RFC 2616 Definition</a></h1>
     839         <p id="rfc.section.A.p.1">Compared to <a href="https://tools.ietf.org/html/rfc2616#section-19.5.1">Section 19.5.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.10"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, the following normative changes reflecting actual implementations have been made:
     840         </p>
     841         <ul>
     842            <li>According to RFC 2616, the disposition type "attachment" only applies to content of type "application/octet-stream". This
     843               restriction has been removed, because recipients in practice do not check the content type, and it also discourages properly
     844               declaring the media type.
     845            </li>
     846            <li>RFC 2616 only allows "quoted-string" for the filename parameter. This would be an exceptional parameter syntax, and also doesn't
     847               reflect actual use.
     848            </li>
     849            <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.
     850            </li>
     851            <li>This specification requires support for the extended parameter encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.8"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>.
     852            </li>
     853         </ul>
     854      </div>
     855      <div id="diffs.compared.to.rfc2183">
     856         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#diffs.compared.to.rfc2183">Differences compared to RFC 2183</a></h1>
     857         <p id="rfc.section.B.p.1"><a href="https://tools.ietf.org/html/rfc2183#section-2">Section 2</a> of <a href="#RFC2183" id="rfc.xref.RFC2183.7"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a> defines several additional disposition parameters: "creation-date", "modification-date", "quoted-date-time", and "size". The
     858            majority of user agents does not implement these, thus they have been omitted from this specification.
     859         </p>
     860      </div>
     861      <div id="alternatives">
     862         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#alternatives">Alternative Approaches to Internationalization</a></h1>
     863         <p id="rfc.section.C.p.1">By default, HTTP header field parameters cannot carry characters outside the ISO-8859-1 (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.2"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>) character encoding (see <a href="#RFC2616" id="rfc.xref.RFC2616.11"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="https://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>). For the "filename" parameter, this of course is an unacceptable restriction.
     864         </p>
     865         <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
     866            Track specifies exactly one solution (<a href="#RFC2231" id="rfc.xref.RFC2231.1"><cite title="MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations">[RFC2231]</cite></a>, clarified and profiled for HTTP in <a href="#RFC5987" id="rfc.xref.RFC5987.9"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>).
     867         </p>
     868         <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
     869            to the RFC 5987 encoding used in this specification.
     870         </p>
     871         <div id="alternatives.rfc2047">
     872            <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;<a href="#alternatives.rfc2047">RFC 2047 Encoding</a></h2>
     873            <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
     874               - 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>:
     875            </p>
     876            <blockquote id="rfc.section.C.1.p.2" cite="http://tools.ietf.org/html/rfc2047#section-5">
     877               <p>An 'encoded-word' MUST NOT appear within a 'quoted-string'.</p>
     878               <p>...</p>
     879               <p>An 'encoded-word' MUST NOT be used in parameter of a MIME Content-Type or Content-Disposition field, or in any structured
     880                  field body except within a 'comment' or 'phrase'.
     881               </p>
     882            </blockquote>
     883            <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
     884               confused by it.
     885            </p>
     886         </div>
     887         <div id="alternatives.percent">
     888            <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;<a href="#alternatives.percent">Percent Encoding</a></h2>
     889            <p id="rfc.section.C.2.p.1">Some user agents accept percent encoded (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="https://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>) sequences of characters. The character encoding being used for decoding depends on various factors, including the encoding
     890               of the referring page, the user agent's locale, its configuration, and also the actual value of the parameter.
     891            </p>
     892            <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
     893               to the user. For those user agents that do implement this it is difficult to predict what character encoding they actually
     894               expect.
     895            </p>
     896         </div>
     897         <div id="alternatives.sniff">
     898            <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;<a href="#alternatives.sniff">Encoding Sniffing</a></h2>
     899            <p id="rfc.section.C.3.p.1">Some user agents inspect the value (which defaults to ISO-8859-1 for the quoted-string form) and switch to UTF-8 when it seems
     900               to be more likely to be the correct interpretation.
     901            </p>
     902            <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>
     903         </div>
     904         <div id="alternatives.implementations">
     905            <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a href="#alternatives.implementations">Implementations (to be removed by RFC Editor before publication)</a></h2>
     906            <p id="rfc.section.C.4.p.1">Unfortunately, as of March 2011, neither the encoding defined in RFCs 2231 and 5987, nor any of the alternate approaches discussed
     907               above was implemented interoperably. Thus, this specification recommends the approach defined in RFC 5987, which at least
     908               has the advantage of actually being specified properly.
     909            </p>
     910            <p id="rfc.section.C.4.p.2">The table below shows the support for the various approaches in the current implementations:</p>
     911            <div id="rfc.table.u.1">
     912               <table class="tt full left" cellpadding="3" cellspacing="0">
     913                  <thead>
     914                     <tr>
     915                        <th>User Agent</th>
     916                        <th>RFC 2231/5987</th>
     917                        <th>RFC 2047</th>
     918                        <th>Percent Encoding</th>
     919                        <th>Encoding Sniffing</th>
     920                     </tr>
     921                  </thead>
     922                  <tbody>
     923                     <tr>
     924                        <td class="left">Chrome</td>
     925                        <td class="left">yes</td>
     926                        <td class="left">yes</td>
     927                        <td class="left">yes</td>
     928                        <td class="left">yes</td>
     929                     </tr>
     930                     <tr>
     931                        <td class="left">Firefox</td>
     932                        <td class="left">yes (*)</td>
     933                        <td class="left">yes</td>
     934                        <td class="left">no</td>
     935                        <td class="left">yes</td>
     936                     </tr>
     937                     <tr>
     938                        <td class="left">Internet Explorer</td>
     939                        <td class="left">yes (**)</td>
     940                        <td class="left">no</td>
     941                        <td class="left">yes</td>
     942                        <td class="left">no</td>
     943                     </tr>
     944                     <tr>
     945                        <td class="left">Konqueror</td>
     946                        <td class="left">yes</td>
     947                        <td class="left">no</td>
     948                        <td class="left">no</td>
     949                        <td class="left">no</td>
     950                     </tr>
     951                     <tr>
     952                        <td class="left">Opera</td>
     953                        <td class="left">yes</td>
     954                        <td class="left">no</td>
     955                        <td class="left">no</td>
     956                        <td class="left">no</td>
     957                     </tr>
     958                     <tr>
     959                        <td class="left">Safari</td>
     960                        <td class="left">no</td>
     961                        <td class="left">no</td>
     962                        <td class="left">no</td>
     963                        <td class="left">yes</td>
     964                     </tr>
     965                  </tbody>
     966               </table>
     967            </div>
     968            <p id="rfc.section.C.4.p.3">(*) Does not implement the fallback behavior to "filename" described in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;4.3</a>; a fix is planned for Firefox 5.
     969            </p>
     970            <p id="rfc.section.C.4.p.4">(**) Starting with Internet Explorer 9, but only implements UTF-8.</p>
     971         </div>
     972      </div>
     973      <div id="advice.generating">
     974         <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a href="#advice.generating">Advice on Generating Content-Disposition Header Fields</a></h1>
     975         <p id="rfc.section.D.p.1">To successfully interoperate with existing and future user agents, senders of the Content-Disposition header field are advised
     976            to:
     977         </p>
     978         <p id="rfc.section.D.p.2"></p>
     979         <ul>
     980            <li>Include a "filename" parameter when US-ASCII (<a href="#US-ASCII" id="rfc.xref.US-ASCII.1"><cite title="Coded Character Set -- 7-bit American Standard Code for Information Interchange">[US-ASCII]</cite></a>) is sufficiently expressive.
     981            </li>
     982            <li>Use the 'token' form of the filename parameter only when it does not contain disallowed characters (e.g., spaces); in such
     983               cases, the quoted-string form should be used.
     984            </li>
     985            <li>Avoid including the percent character followed by two hexadecimal characters (e.g., %A9) in the filename parameter, since
     986               some existing implementations consider it to be an escape character, while others will pass it through unchanged.
     987            </li>
     988            <li>Avoid including the "\" character in the quoted-string form of the filename parameter, as escaping is not implemented by some
     989               user agents, and can be considered as an illegal path character.
     990            </li>
     991            <li>Avoid using non-ASCII characters in the filename parameter. Although most existing implementations will decode them as ISO-8859-1,
     992               some will apply heuristics to detect UTF-8, and thus might fail on certain names.
     993            </li>
     994            <li>Include a "filename*" parameter where the desired filename cannot be expressed faithfully using the "filename" form. Note
     995               that legacy user agents will not process this, and will fall back to using the "filename" parameter's content.
     996            </li>
     997            <li>When a "filename*" parameter is sent, to also generate a "filename" parameter as a fallback for user agents that do not support
     998               the "filename*" form, if possible. This can be done by substituting characters with US-ASCII sequences (e.g., Unicode character
     999               point U+00E4 (LATIN SMALL LETTER A WITH DIARESIS) by "ae"). Note that this may not be possible in some locales.
     1000            </li>
     1001            <li>When a "filename" parameter is included as a fallback (as per above), "filename" should occur first, due to parsing problems
     1002               in some existing implementations. <span class="comment" id="fallbackbug">[<a href="#fallbackbug" class="smpl">fallbackbug</a>: Firefox is known to pick the wrong parameter; a bug fix is scheduled for Firefox 5. --jre]</span> <span class="comment" id="NOTE-TO-RFC-EDITOR">[<a href="#NOTE-TO-RFC-EDITOR" class="smpl">NOTE-TO-RFC-EDITOR</a>: PLEASE REMOVE THIS AND THE PRECEDING COMMENT BEFORE PUBLICATION AS RFC. --jre]</span>
     1003            </li>
     1004            <li>Use UTF-8 as the encoding of the "filename*" parameter, when present, because at least one existing implementation only implements
     1005               that encoding.
     1006            </li>
     1007         </ul>
     1008         <p id="rfc.section.D.p.3">Note that this advice is based upon UA behaviour at the time of writing, and might be superseded. At the time of publication
     1009            of this document, &lt;<a href="http://purl.org/NET/http/content-disposition-tests">http://purl.org/NET/http/content-disposition-tests</a>&gt; provides an overview of current levels of support in various implementations.
     1010         </p>
     1011      </div>
     1012      <div id="change.log">
     1013         <h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
     1014         <p id="rfc.section.E.p.1">Note: the issues names in the change log entries for draft-reschke-rfc2183-in-http refer to &lt;<a href="http://greenbytes.de/tech/webdav/draft-reschke-rfc2183-in-http-issues.html">http://greenbytes.de/tech/webdav/draft-reschke-rfc2183-in-http-issues.html</a>&gt;.
     1015         </p>
     1016         <div>
     1017            <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;Since draft-reschke-rfc2183-in-http-00
     1018            </h2>
     1019            <p id="rfc.section.E.1.p.1">Adjust terminology ("header" -&gt; "header field"). Update rfc2231-in-http reference.</p>
     1020         </div>
     1021         <div>
     1022            <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;Since draft-reschke-rfc2183-in-http-01
     1023            </h2>
     1024            <p id="rfc.section.E.2.p.1">Update rfc2231-in-http reference. Actually define the "filename" parameter. Add internationalization considerations. Add examples
     1025               using the RFC 5987 encoding. Add overview over other approaches, plus a table reporting implementation status. Add and resolve
     1026               issue "nodep2183". Add issues "asciivsiso", "deplboth", "quoted", and "registry".
     1027            </p>
     1028         </div>
     1029         <div>
     1030            <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a>&nbsp;Since draft-reschke-rfc2183-in-http-02
     1031            </h2>
     1032            <p id="rfc.section.E.3.p.1">Add and close issue "docfallback". Close issues "asciivsiso", "deplboth", "quoted", and "registry".</p>
     1033         </div>
     1034         <div>
     1035            <h2 id="rfc.section.E.4"><a href="#rfc.section.E.4">E.4</a>&nbsp;Since draft-reschke-rfc2183-in-http-03
     1036            </h2>
     1037            <p id="rfc.section.E.4.p.1">Updated to be a Working Draft of the IETF HTTPbis Working Group.</p>
     1038         </div>
     1039         <div id="changes.since.00">
     1040            <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;<a href="#changes.since.00">Since draft-ietf-httpbis-content-disp-00</a></h2>
     1041            <p id="rfc.section.E.5.p.1">Closed issues: </p>
     1042            <ul>
     1043               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/242">http://tools.ietf.org/wg/httpbis/trac/ticket/242</a>&gt;: "handling of unknown disposition types"
     1044               </li>
     1045            </ul>
     1046            <p id="rfc.section.E.5.p.2">Slightly updated the notes about the proposed fallback behavior.</p>
     1047         </div>
     1048         <div id="changes.since.01">
     1049            <h2 id="rfc.section.E.6"><a href="#rfc.section.E.6">E.6</a>&nbsp;<a href="#changes.since.01">Since draft-ietf-httpbis-content-disp-01</a></h2>
     1050            <p id="rfc.section.E.6.p.1">Various editorial improvements.</p>
     1051         </div>
     1052         <div id="changes.since.02">
     1053            <h2 id="rfc.section.E.7"><a href="#rfc.section.E.7">E.7</a>&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-content-disp-02</a></h2>
     1054            <p id="rfc.section.E.7.p.1">Closed issues: </p>
     1055            <ul>
     1056               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/244">http://tools.ietf.org/wg/httpbis/trac/ticket/244</a>&gt;: "state that repeating parameters are invalid"
     1057               </li>
     1058               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/245">http://tools.ietf.org/wg/httpbis/trac/ticket/245</a>&gt;: "warn about %xx in filenames being misinterpreted"
     1059               </li>
     1060               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/246">http://tools.ietf.org/wg/httpbis/trac/ticket/246</a>&gt;: "mention control chars when talking about postprecessing the filename parameter"
     1061               </li>
     1062            </ul>
     1063            <p id="rfc.section.E.7.p.2">Update <a href="#alternatives.implementations" title="Implementations (to be removed by RFC Editor before publication)">Appendix&nbsp;C.4</a>; Opera 10.63 RC implements the recommended fallback behavior.
     1064            </p>
     1065         </div>
     1066         <div id="changes.since.03">
     1067            <h2 id="rfc.section.E.8"><a href="#rfc.section.E.8">E.8</a>&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-content-disp-03</a></h2>
     1068            <p id="rfc.section.E.8.p.1">Closed issues: </p>
     1069            <ul>
     1070               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/252">http://tools.ietf.org/wg/httpbis/trac/ticket/252</a>&gt;: "'modification-date' *is* implemented in Konq 4.5"
     1071               </li>
     1072               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/253">http://tools.ietf.org/wg/httpbis/trac/ticket/253</a>&gt;: "clarify what LWS means for the Content-Disp grammar"
     1073               </li>
     1074               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/258">http://tools.ietf.org/wg/httpbis/trac/ticket/258</a>&gt;: "Avoid passive voice in message requirements"
     1075               </li>
     1076               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/263">http://tools.ietf.org/wg/httpbis/trac/ticket/263</a>&gt;: "text about historical percent-decoding unclear"
     1077               </li>
     1078               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/264">http://tools.ietf.org/wg/httpbis/trac/ticket/264</a>&gt;: "add explanation of language tagging"
     1079               </li>
     1080               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/265">http://tools.ietf.org/wg/httpbis/trac/ticket/265</a>&gt;: "Clarify that C-D spec does not apply to multipart upload"
     1081               </li>
     1082            </ul>
     1083         </div>
     1084         <div id="changes.since.04">
     1085            <h2 id="rfc.section.E.9"><a href="#rfc.section.E.9">E.9</a>&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-content-disp-04</a></h2>
     1086            <p id="rfc.section.E.9.p.1">Updated implementation information (Chrome 9 implements RFC 5987, IE 9 RC implements it for UTF-8 only).</p>
     1087            <p id="rfc.section.E.9.p.2">Clarify who requirements are on, add a section discussing conformance and handling of invalid field values in general.</p>
     1088            <p id="rfc.section.E.9.p.3">Closed issues: </p>
     1089            <ul>
     1090               <li>&lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/243">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/243</a>&gt;: "avoid stating ISO-8859-1 default for header param" (the default is still mentioned, but it was clarified what it applies
     1091                  to).
     1092               </li>
     1093               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/272">http://tools.ietf.org/wg/httpbis/trac/ticket/272</a>&gt;: "Path Separator Characters"
     1094               </li>
     1095            </ul>
     1096         </div>
     1097         <div id="changes.since.05">
     1098            <h2 id="rfc.section.E.10"><a href="#rfc.section.E.10">E.10</a>&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-content-disp-05</a></h2>
     1099            <p id="rfc.section.E.10.p.1">Editorial changes: Fixed two typos where the new Conformance section said "Content-Location" instead of "Content-Disposition".
     1100               Cleaned up terminology ("user agent", "recipient", "sender", "message body", ...). Stated what the escape character for quoted-string
     1101               is. Explained a use case for "inline" disposition type. Updated implementation notes with respect to the fallback behavior.
     1102            </p>
     1103            <p id="rfc.section.E.10.p.2">Added appendix "Advice on Generating Content-Disposition Header Fields".</p>
     1104         </div>
     1105         <div id="changes.since.06">
     1106            <h2 id="rfc.section.E.11"><a href="#rfc.section.E.11">E.11</a>&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-content-disp-06</a></h2>
     1107            <p id="rfc.section.E.11.p.1">Closed issues: </p>
     1108            <ul>
     1109               <li>&lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/278">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/278</a>&gt;: "conformance language"
     1110               </li>
     1111            </ul>
     1112         </div>
     1113         <div id="changes.since.07">
     1114            <h2 id="rfc.section.E.12"><a href="#rfc.section.E.12">E.12</a>&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-content-disp-07</a></h2>
     1115            <p id="rfc.section.E.12.p.1">Rephrase the requirement about well-known file system locations, and also clarify that by "last path segment" we mean the
     1116               actual filename. Added a forward reference from "invalid" to the section that defines a valid header field.
     1117            </p>
     1118         </div>
     1119         <div id="changes.since.08">
     1120            <h2 id="rfc.section.E.13"><a href="#rfc.section.E.13">E.13</a>&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-content-disp-08</a></h2>
     1121            <p id="rfc.section.E.13.p.1">Update: Internet Explorer 9 is released. Various editorial improvements. Add US-ASCII reference. Strengthen file extension
     1122               handling requirement to MUST for those recipients that actually use file extensions to map media types.
     1123            </p>
     1124         </div>
     1125      </div>
    10471126      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    10481127      <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> <a href="#rfc.index.U">U</a>
     
    11091188         </ul>
    11101189      </div>
     1190      <div class="avoidbreak">
     1191         <h1 id="rfc.authors"><a href="#rfc.authors">Author's Address</a></h1>
     1192         <p><b>Julian F. Reschke</b><br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Email: <a href="mailto:julian.reschke@greenbytes.de">julian.reschke@greenbytes.de</a><br>URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a></p>
     1193      </div>
    11111194   </body>
    11121195</html>
Note: See TracChangeset for help on using the changeset viewer.