Ignore:
Timestamp:
14/06/14 11:20:37 (7 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/00/draft-ietf-httpbis-content-disp.html

    r986 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 {
    3940  font-style: normal;
    4041}
    41 dd {
    42   margin-right: 2em;
    43 }
    4442dl {
    4543  margin-left: 2em;
    4644}
    47 
    4845ul.empty {
    4946  list-style-type: none;
     
    5956}
    6057h1 {
    61   font-size: 14pt;
     58  font-size: 130%;
    6259  line-height: 21pt;
    6360  page-break-after: avoid;
     
    6663  page-break-before: always;
    6764}
    68 h1 a {
    69   color: #333333;
    70 }
    7165h2 {
    72   font-size: 12pt;
     66  font-size: 120%;
    7367  line-height: 15pt;
    7468  page-break-after: avoid;
    7569}
    76 h3, h4, h5, h6 {
    77   font-size: 10pt;
     70h3 {
     71  font-size: 110%;
    7872  page-break-after: avoid;
    7973}
    80 h2 a, h3 a, h4 a, h5 a, h6 a {
     74h4, h5, h6 {
     75  page-break-after: avoid;
     76}
     77h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
    8178  color: black;
    8279}
     
    8683li {
    8784  margin-left: 2em;
    88   margin-right: 2em;
    8985}
    9086ol {
    9187  margin-left: 2em;
    92   margin-right: 2em;
     88}
     89ol.la {
     90  list-style-type: lower-alpha;
     91}
     92ol.ua {
     93  list-style-type: upper-alpha;
    9394}
    9495ol p {
     
    9798p {
    9899  margin-left: 2em;
    99   margin-right: 2em;
    100100}
    101101pre {
     
    103103  background-color: lightyellow;
    104104  padding: .25em;
     105  page-break-inside: avoid;
    105106}
    106107pre.text2 {
     
    131132table.tt {
    132133  vertical-align: top;
     134  border-color: gray;
     135}
     136table.tt th {
     137  border-color: gray;
     138}
     139table.tt td {
     140  border-color: gray;
     141}
     142table.all {
     143  border-style: solid;
     144  border-width: 2px;
    133145}
    134146table.full {
    135   border-style: outset;
    136   border-width: 1px;
    137 }
    138 table.headers {
    139   border-style: outset;
    140   border-width: 1px;
     147  border-style: solid;
     148  border-width: 2px;
    141149}
    142150table.tt td {
    143151  vertical-align: top;
    144152}
     153table.all td {
     154  border-style: solid;
     155  border-width: 1px;
     156}
    145157table.full td {
    146   border-style: inset;
     158  border-style: none solid;
    147159  border-width: 1px;
    148160}
     
    150162  vertical-align: top;
    151163}
     164table.all th {
     165  border-style: solid;
     166  border-width: 1px;
     167}
    152168table.full th {
    153   border-style: inset;
    154   border-width: 1px;
     169  border-style: solid;
     170  border-width: 1px 1px 2px 1px;
    155171}
    156172table.headers th {
    157   border-style: none none inset none;
    158   border-width: 1px;
     173  border-style: none none solid none;
     174  border-width: 2px;
    159175}
    160176table.left {
     
    171187  caption-side: bottom;
    172188  font-weight: bold;
    173   font-size: 9pt;
     189  font-size: 10pt;
    174190  margin-top: .5em;
    175191}
     
    178194  border-spacing: 1px;
    179195  width: 95%;
    180   font-size: 10pt;
     196  font-size: 11pt;
    181197  color: white;
    182198}
     
    186202td.topnowrap {
    187203  vertical-align: top;
    188   white-space: nowrap; 
     204  white-space: nowrap;
    189205}
    190206table.header td {
     
    203219  display:table-header-group;
    204220}
    205 ul.toc {
     221ul.toc, ul.toc ul {
    206222  list-style: none;
    207223  margin-left: 1.5em;
    208   margin-right: 0em;
    209224  padding-left: 0em;
    210225}
    211 li.tocline0 {
     226ul.toc li {
    212227  line-height: 150%;
    213228  font-weight: bold;
     229  margin-left: 0em;
     230}
     231ul.toc li li {
     232  line-height: normal;
     233  font-weight: normal;
    214234  font-size: 10pt;
    215235  margin-left: 0em;
    216   margin-right: 0em;
    217 }
    218 li.tocline1 {
    219   line-height: normal;
    220   font-weight: normal;
    221   font-size: 9pt;
    222   margin-left: 0em;
    223   margin-right: 0em;
    224 }
    225 li.tocline2 {
     236}
     237li.excluded {
    226238  font-size: 0pt;
    227239}
     
    229241  margin-left: 0em;
    230242}
    231 ul.ind {
     243.title, .filename, h1, h2, h3, h4 {
     244  font-family: candara, helvetica, arial, sans-serif;
     245}
     246samp, tt, code, pre {
     247  font: consolas, monospace;
     248}
     249ul.ind, ul.ind ul {
    232250  list-style: none;
    233251  margin-left: 1.5em;
    234   margin-right: 0em;
    235252  padding-left: 0em;
    236253  page-break-before: avoid;
    237254}
    238 li.indline0 {
     255ul.ind li {
    239256  font-weight: bold;
    240257  line-height: 200%;
    241258  margin-left: 0em;
    242   margin-right: 0em;
    243 }
    244 li.indline1 {
     259}
     260ul.ind li li {
    245261  font-weight: normal;
    246262  line-height: 150%;
    247263  margin-left: 0em;
    248   margin-right: 0em;
    249264}
    250265.avoidbreak {
     
    273288  font-weight: bold;
    274289  text-align: center;
    275   font-size: 9pt;
     290  font-size: 10pt;
    276291}
    277292.filename {
    278293  color: #333333;
     294  font-size: 75%;
    279295  font-weight: bold;
    280   font-size: 12pt;
    281296  line-height: 21pt;
    282297  text-align: center;
     
    285300  font-weight: bold;
    286301}
    287 .hidden {
    288   display: none;
    289 }
    290302.left {
    291303  text-align: left;
     
    295307}
    296308.title {
    297   color: #990000;
    298   font-size: 18pt;
     309  color: green;
     310  font-size: 150%;
    299311  line-height: 18pt;
    300312  font-weight: bold;
     
    302314  margin-top: 36pt;
    303315}
    304 .vcardline {
    305   display: block;
    306 }
    307316.warning {
    308   font-size: 14pt;
     317  font-size: 130%;
    309318  background-color: yellow;
    310319}
     
    315324    display: none;
    316325  }
    317  
     326
    318327  a {
    319328    color: black;
     
    330339    background-color: white;
    331340    vertical-align: top;
    332     font-size: 12pt;
    333   }
    334 
    335   ul.toc a::after {
     341    font-size: 110%;
     342  }
     343
     344  ul.toc a:nth-child(2)::after {
    336345    content: leader('.') target-counter(attr(href), page);
    337346  }
    338  
    339   a.iref {
     347
     348  ul.ind li li a {
    340349    content: target-counter(attr(href), page);
    341350  }
    342  
     351
    343352  .print2col {
    344353    column-count: 2;
     
    350359@page {
    351360  @top-left {
    352        content: "Internet-Draft"; 
    353   } 
     361       content: "Internet-Draft";
     362  }
    354363  @top-right {
    355        content: "September 2010"; 
    356   } 
     364       content: "September 2010";
     365  }
    357366  @top-center {
    358        content: "Content-Disposition in HTTP"; 
    359   } 
     367       content: "Content-Disposition in HTTP";
     368  }
    360369  @bottom-left {
    361        content: "Reschke"; 
    362   } 
     370       content: "Reschke";
     371  }
    363372  @bottom-center {
    364        content: "Standards Track";
    365   } 
     373       content: "Expires March 7, 2011";
     374  }
    366375  @bottom-right {
    367        content: "[Page " counter(page) "]"; 
    368   } 
    369 }
    370 
    371 @page:first { 
     376       content: "[Page " counter(page) "]";
     377  }
     378}
     379
     380@page:first {
    372381    @top-left {
    373382      content: normal;
     
    397406      <link rel="Appendix" title="C Alternative Approaches to Internationalization" href="#rfc.section.C">
    398407      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    399       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.522, 2010-08-31 15:02:33, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     408      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    400409      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    401410      <meta name="dct.creator" content="Reschke, J. F.">
     
    417426            </tr>
    418427            <tr>
    419                <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
     428               <td class="left">Updates: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    420429               </td>
    421430               <td class="right">September 3, 2010</td>
     
    432441      </table>
    433442      <p class="title">Use of the Content-Disposition&nbsp;Header&nbsp;Field in the Hypertext&nbsp;Transfer&nbsp;Protocol&nbsp;(HTTP)<br><span class="filename">draft-ietf-httpbis-content-disp-00</span></p>
    434       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
     443      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    435444      <p>HTTP/1.1 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard.
    436445         This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization
    437446         aspects.
    438       </p> 
    439       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor before publication)</a></h1> 
     447      </p>
     448      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor before publication)</a></h1>
    440449      <p>This specification is expected to replace the definition of Content-Disposition in the HTTP/1.1 specification, as currently
    441450         revised by the IETF HTTPbis working group. See also &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/123">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/123</a>&gt;.
    442       </p> 
     451      </p>
    443452      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    444453         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;.
    445       </p>   
    446       <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
    447       <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
    448       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
    449          working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
    450454      </p>
    451       <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
    452          documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
    453          in progress”.
    454       </p>
    455       <p>This Internet-Draft will expire on March 7, 2011.</p>
    456       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    457       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    458       <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="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
    459          and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
    460          text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
    461          BSD License.
    462       </p>
     455      <div id="rfc.status">
     456         <h1><a href="#rfc.status">Status of This Memo</a></h1>
     457         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
     458         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
     459            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>.
     460         </p>
     461         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     462            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     463            in progress”.
     464         </p>
     465         <p>This Internet-Draft will expire on March 7, 2011.</p>
     466      </div>
     467      <div id="rfc.copyrightnotice">
     468         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     469         <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     470         <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
     471            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
     472            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
     473            BSD License.
     474         </p>
     475      </div>
    463476      <hr class="noprint">
    464477      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    465478      <ul class="toc">
    466          <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a></li>
    467          <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2">Notational Conventions</a></li>
    468          <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#header.field.definition">Header Field Definition</a><ul class="toc">
    469                <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.1">Grammar</a></li>
    470                <li class="tocline1">3.2&nbsp;&nbsp;&nbsp;<a href="#disposition.type">Disposition Type</a></li>
    471                <li class="tocline1">3.3&nbsp;&nbsp;&nbsp;<a href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></li>
    472                <li class="tocline1">3.4&nbsp;&nbsp;&nbsp;<a href="#disposition.parameter.extensionsS">Disposition Parameter: Extensions</a></li>
    473                <li class="tocline1">3.5&nbsp;&nbsp;&nbsp;<a href="#extensibility">Extensibility</a></li>
     479         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a></li>
     480         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2">Notational Conventions</a></li>
     481         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.definition">Header Field Definition</a><ul>
     482               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.1">Grammar</a></li>
     483               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#disposition.type">Disposition Type</a></li>
     484               <li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></li>
     485               <li><a href="#rfc.section.3.4">3.4</a>&nbsp;&nbsp;&nbsp;<a href="#disposition.parameter.extensionsS">Disposition Parameter: Extensions</a></li>
     486               <li><a href="#rfc.section.3.5">3.5</a>&nbsp;&nbsp;&nbsp;<a href="#extensibility">Extensibility</a></li>
    474487            </ul>
    475488         </li>
    476          <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4">Examples</a></li>
    477          <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#i18n">Internationalization Considerations</a></li>
    478          <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
    479          <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#iana.considerations">IANA Considerations</a><ul class="toc">
    480                <li class="tocline1">7.1&nbsp;&nbsp;&nbsp;<a href="#registry">Registry for Disposition Values and Parameter</a></li>
    481                <li class="tocline1">7.2&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
     489         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4">Examples</a></li>
     490         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#i18n">Internationalization Considerations</a></li>
     491         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
     492         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#iana.considerations">IANA Considerations</a><ul>
     493               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#registry">Registry for Disposition Values and Parameter</a></li>
     494               <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
    482495            </ul>
    483496         </li>
    484          <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.8">Acknowledgements</a></li>
    485          <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul class="toc">
    486                <li class="tocline1">9.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    487                <li class="tocline1">9.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     497         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.8">Acknowledgements</a></li>
     498         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     499               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     500               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    488501            </ul>
    489502         </li>
    490          <li class="tocline0"><a href="#rfc.authors">Author's Address</a></li>
    491          <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc2616">Changes from the RFC 2616 Definition</a></li>
    492          <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#diffs.compared.to.rfc2183">Differences compared to RFC 2183</a></li>
    493          <li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#alternatives">Alternative Approaches to Internationalization</a><ul class="toc">
    494                <li class="tocline1">C.1&nbsp;&nbsp;&nbsp;<a href="#alternatives.rfc2047">RFC 2047 Encoding</a></li>
    495                <li class="tocline1">C.2&nbsp;&nbsp;&nbsp;<a href="#alternatives.percent">Percent Encoding</a></li>
    496                <li class="tocline1">C.3&nbsp;&nbsp;&nbsp;<a href="#alternatives.sniff">Encoding Sniffing</a></li>
    497                <li class="tocline1">C.4&nbsp;&nbsp;&nbsp;<a href="#alternatives.implementations">Implementations</a></li>
     503         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc2616">Changes from the RFC 2616 Definition</a></li>
     504         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#diffs.compared.to.rfc2183">Differences compared to RFC 2183</a></li>
     505         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#alternatives">Alternative Approaches to Internationalization</a><ul>
     506               <li><a href="#rfc.section.C.1">C.1</a>&nbsp;&nbsp;&nbsp;<a href="#alternatives.rfc2047">RFC 2047 Encoding</a></li>
     507               <li><a href="#rfc.section.C.2">C.2</a>&nbsp;&nbsp;&nbsp;<a href="#alternatives.percent">Percent Encoding</a></li>
     508               <li><a href="#rfc.section.C.3">C.3</a>&nbsp;&nbsp;&nbsp;<a href="#alternatives.sniff">Encoding Sniffing</a></li>
     509               <li><a href="#rfc.section.C.4">C.4</a>&nbsp;&nbsp;&nbsp;<a href="#alternatives.implementations">Implementations</a></li>
    498510            </ul>
    499511         </li>
    500          <li class="tocline0">D.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
    501                <li class="tocline1">D.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since draft-reschke-rfc2183-in-http-00</a></li>
    502                <li class="tocline1">D.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.2">Since draft-reschke-rfc2183-in-http-01</a></li>
    503                <li class="tocline1">D.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.3">Since draft-reschke-rfc2183-in-http-02</a></li>
    504                <li class="tocline1">D.4&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.4">Since draft-reschke-rfc2183-in-http-03</a></li>
     512         <li><a href="#rfc.section.D">D.</a>&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
     513               <li><a href="#rfc.section.D.1">D.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since draft-reschke-rfc2183-in-http-00</a></li>
     514               <li><a href="#rfc.section.D.2">D.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.2">Since draft-reschke-rfc2183-in-http-01</a></li>
     515               <li><a href="#rfc.section.D.3">D.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.3">Since draft-reschke-rfc2183-in-http-02</a></li>
     516               <li><a href="#rfc.section.D.4">D.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.4">Since draft-reschke-rfc2183-in-http-03</a></li>
    505517            </ul>
    506518         </li>
    507          <li class="tocline0"><a href="#rfc.index">Index</a></li>
     519         <li><a href="#rfc.index">Index</a></li>
     520         <li><a href="#rfc.authors">Author's Address</a></li>
    508521      </ul>
    509       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    510       <p id="rfc.section.1.p.1">HTTP/1.1 defines the Content-Disposition response header field in <a href="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>):
    511       </p>
    512       <blockquote id="rfc.section.1.p.2" cite="http://tools.ietf.org/html/rfc2616#section-15.5">
    513          <p>Content-Disposition is not part of the HTTP standard, but since it is widely implemented, we are documenting its use and risks
    514             for implementers.
    515          </p>
    516       </blockquote>
    517       <p id="rfc.section.1.p.3">This specification takes over the definition and registration of Content-Disposition, as used in HTTP. Based on interoperability
    518          testing with existing User Agents, it fully defines a profile of the features defined in the Multipurpose Internet Mail Extensions
    519          (MIME) variant (<a href="#RFC2183" id="rfc.xref.RFC2183.1"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>) of the header field, and also clarifies internationalization aspects.
    520       </p>
    521       <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;Notational Conventions
    522       </h1>
    523       <p id="rfc.section.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
    524          in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    525       </p>
    526       <p id="rfc.section.2.p.2">This specification uses the augmented BNF notation defined in <a href="http://tools.ietf.org/html/rfc2616#section-2.1">Section 2.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, including its rules for linear whitespace (LWS).
    527       </p>
    528       <div id="rfc.iref.h.1"></div>
    529       <div id="rfc.iref.c.1"></div>
    530       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.field.definition" href="#header.field.definition">Header Field Definition</a></h1>
    531       <p id="rfc.section.3.p.1">The Content-Disposition response header field is used to convey additional information about how to process the response payload,
    532          and also can be used to attach additional metadata, such as the filename.
    533       </p>
    534       <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;Grammar
    535       </h2>
    536       <div id="rfc.figure.u.1"></div><pre class="inline">  content-disposition = "Content-Disposition" ":"
     522      <div id="introduction">
     523         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     524         <p id="rfc.section.1.p.1">HTTP/1.1 defines the Content-Disposition response header field in <a href="https://tools.ietf.org/html/rfc2616#section-19.5.1">Section 19.5.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, but points out that it is not part of the HTTP/1.1 Standard (<a href="https://tools.ietf.org/html/rfc2616#section-15.5" id="rfc.xref.RFC2616.2">Section 15.5</a>):
     525         </p>
     526         <blockquote id="rfc.section.1.p.2" cite="http://tools.ietf.org/html/rfc2616#section-15.5">
     527            <p>Content-Disposition is not part of the HTTP standard, but since it is widely implemented, we are documenting its use and risks
     528               for implementers.
     529            </p>
     530         </blockquote>
     531         <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
     532            testing with existing User Agents, it fully defines a profile of the features defined in the Multipurpose Internet Mail Extensions
     533            (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.
     534         </p>
     535      </div>
     536      <div>
     537         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;Notational Conventions
     538         </h1>
     539         <p id="rfc.section.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
     540            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>.
     541         </p>
     542         <p id="rfc.section.2.p.2">This specification uses the augmented BNF notation defined in <a href="https://tools.ietf.org/html/rfc2616#section-2.1">Section 2.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, including its rules for linear whitespace (LWS).
     543         </p>
     544      </div>
     545      <div id="header.field.definition">
     546         <div id="rfc.iref.h.1"></div>
     547         <div id="rfc.iref.c.1"></div>
     548         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#header.field.definition">Header Field Definition</a></h1>
     549         <p id="rfc.section.3.p.1">The Content-Disposition response header field is used to convey additional information about how to process the response payload,
     550            and also can be used to attach additional metadata, such as the filename.
     551         </p>
     552         <div>
     553            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;Grammar
     554            </h2>
     555            <div id="rfc.figure.u.1"></div><pre class="inline">  content-disposition = "Content-Disposition" ":"
    537556                         disposition-type *( ";" disposition-parm )
    538557
     
    549568                      | ext-token "=" ext-value
    550569  ext-token           = &lt;the characters in token, followed by "*"&gt;
    551 </pre><div id="rfc.figure.u.2"></div>
    552       <p>Defined in <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>:
    553       </p>  <pre class="inline">  token       = &lt;token, defined in <a href="#RFC2616" id="rfc.xref.RFC2616.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>&gt;
    554   value       = &lt;value, defined in <a href="#RFC2616" id="rfc.xref.RFC2616.6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-3.6">Section 3.6</a>&gt;
    555 </pre><div id="rfc.figure.u.3"></div>
    556       <p>Defined in <a href="#RFC5987" id="rfc.xref.RFC5987.1"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>:
    557       </p>  <pre class="inline">  ext-value   = &lt;ext-value, defined in <a href="#RFC5987" id="rfc.xref.RFC5987.2"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>, <a href="http://tools.ietf.org/html/rfc5987#section-3.2">Section 3.2</a>&gt;
    558 </pre><h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="disposition.type" href="#disposition.type">Disposition Type</a></h2>
    559       <p id="rfc.section.3.2.p.1">If the disposition type matches "attachment" (case-insensitively), this indicates that the user agent should not display the
    560          response, but directly enter a "save as..." dialog.
    561       </p>
    562       <p id="rfc.section.3.2.p.2">On the other hand, if it matches "inline" (case-insensitively), this implies default processing.</p>
    563       <p id="rfc.section.3.2.p.3">Other disposition types <em class="bcp14">SHOULD</em> be handled the same way as "attachment" (see also <a href="#RFC2183" id="rfc.xref.RFC2183.2"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>, <a href="http://tools.ietf.org/html/rfc2183#section-2.8">Section 2.8</a>).
    564       </p>
    565       <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="disposition.parameter.filename" href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></h2>
    566       <p id="rfc.section.3.3.p.1">The parameters "filename" and "filename*", to be matched case-insensitively, provide information on how to construct a filename
    567          for storing the message payload.
    568       </p>
    569       <p id="rfc.section.3.3.p.2">Depending on the disposition type, this information might be used right away (in the "save as..." interaction caused for the
    570          "attachment" disposition type), or later on (for instance, when the user decides to save the contents of the current page
    571          being displayed).
    572       </p>
    573       <p id="rfc.section.3.3.p.3">"filename" and "filename*" behave the same, except that "filename*" uses the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.3"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>, allowing the use of characters not present in the ISO-8859-1 character set (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>). When both "filename" and "filename*" are present, a recipient <em class="bcp14">SHOULD</em> pick "filename*" and ignore "filename" - this will make it possible to send the same header value to clients that do not support
    574          "filename*".
    575       </p>
    576       <p id="rfc.section.3.3.p.4">It is essential that user agents treat the specified filename as advisory only, thus be very careful in extracting the desired
    577          information. In particular:
    578       </p>
    579       <ul>
    580          <li>
    581             <p>When the value contains path separator characters, all but the last segment <em class="bcp14">SHOULD</em> be ignored. This prevents unintentional overwriting of well-known file system location (such as "/etc/passwd").
    582             </p>
    583          </li>
    584          <li>
    585             <p>Many platforms do not use Internet Media Types (<a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>) to hold type information in the file system, but rely on filename extensions instead. Trusting the server-provided file
    586                extension could introduce a privilege escalation when later on the file is opened locally (consider ".exe"). Thus, recipients
    587                need to ensure that a file extension is used that is safe, optimally matching the media type of the received payload.
    588             </p>
    589          </li>
    590          <li>
    591             <p>Other aspects recipients need to be aware of are names that have a special meaning in the filesystem or in shell commands,
    592                such as "." and "..", "~", "|", and also device names.
    593             </p>
    594          </li>
    595       </ul>
    596       <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="disposition.parameter.extensionsS" href="#disposition.parameter.extensionsS">Disposition Parameter: Extensions</a></h2>
    597       <p id="rfc.section.3.4.p.1">To enable future extensions, unknown parameters <em class="bcp14">SHOULD</em> be ignored (see also <a href="#RFC2183" id="rfc.xref.RFC2183.3"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>, <a href="http://tools.ietf.org/html/rfc2183#section-2.8">Section 2.8</a>).
    598       </p>
    599       <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a id="extensibility" href="#extensibility">Extensibility</a></h2>
    600       <p id="rfc.section.3.5.p.1">Note that <a href="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
    601          using Content-Disposition, such as MIME and HTTP. Therefore, not all registered values may make sense in the context of HTTP.
    602       </p>
    603       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;Examples
    604       </h1>
    605       <div id="rfc.figure.u.4"></div>
    606       <p>Direct UA to show "save as" dialog, with a filename of "foo.html":</p>  <pre class="text">Content-Disposition: Attachment; filename=foo.html
    607 </pre><div id="rfc.figure.u.5"></div>
    608       <p>Direct UA to behave as if the Content-Disposition header field wasn't present, but to remember the filename "foo.html" for
    609          a subsequent save operation:
    610       </p>  <pre class="text">Content-Disposition: INLINE; FILENAME= "foo.html"
    611 </pre><div id="rfc.figure.u.6"></div>
    612       <p>Direct UA to show "save as" dialog, with a filename of "an example":</p>  <pre class="text">Content-Disposition: Attachment; Filename*=UTF-8'<b>en</b>'an<b>%20</b>example
    613 </pre>  <p>Note that this example uses the extended encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.4"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a> to specify that the natural language of the filename is English, and also to encode the space character which is not allowed
    614          in the token production.
    615       </p>
    616       <div id="rfc.figure.u.7"></div>
    617       <p>Direct UA to show "save as" dialog, with a filename containing the Unicode character U+20AC (EURO SIGN):</p>  <pre class="text">Content-Disposition: attachment; filename*= UTF-8''<b>%e2%82%ac</b>%20rates
    618 </pre>  <p>Here, the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.5"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a> is also used to encode the non-ISO-8859-1 character.
    619       </p>
    620       <div id="rfc.figure.u.8"></div>
    621       <p>Same as above, but adding the "filename" parameter for compatibility with user agents not implementing RFC 5987:</p>  <pre class="text">Content-Disposition: attachment; filename="EURO rates";
     570</pre><div id="rfc.figure.u.2"></div>
     571            <p>Defined in <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>:
     572            </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;
     573  value       = &lt;value, defined in <a href="#RFC2616" id="rfc.xref.RFC2616.6"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="https://tools.ietf.org/html/rfc2616#section-3.6">Section 3.6</a>&gt;
     574</pre><div id="rfc.figure.u.3"></div>
     575            <p>Defined in <a href="#RFC5987" id="rfc.xref.RFC5987.1"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>:
     576            </p><pre class="inline">  ext-value   = &lt;ext-value, defined in <a href="#RFC5987" id="rfc.xref.RFC5987.2"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>, <a href="https://tools.ietf.org/html/rfc5987#section-3.2">Section 3.2</a>&gt;
     577</pre></div>
     578         <div id="disposition.type">
     579            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#disposition.type">Disposition Type</a></h2>
     580            <p id="rfc.section.3.2.p.1">If the disposition type matches "attachment" (case-insensitively), this indicates that the user agent should not display the
     581               response, but directly enter a "save as..." dialog.
     582            </p>
     583            <p id="rfc.section.3.2.p.2">On the other hand, if it matches "inline" (case-insensitively), this implies default processing.</p>
     584            <p id="rfc.section.3.2.p.3">Other disposition types <em class="bcp14">SHOULD</em> be handled the same way as "attachment" (see also <a href="#RFC2183" id="rfc.xref.RFC2183.2"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>, <a href="https://tools.ietf.org/html/rfc2183#section-2.8">Section 2.8</a>).
     585            </p>
     586         </div>
     587         <div id="disposition.parameter.filename">
     588            <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#disposition.parameter.filename">Disposition Parameter: 'Filename'</a></h2>
     589            <p id="rfc.section.3.3.p.1">The parameters "filename" and "filename*", to be matched case-insensitively, provide information on how to construct a filename
     590               for storing the message payload.
     591            </p>
     592            <p id="rfc.section.3.3.p.2">Depending on the disposition type, this information might be used right away (in the "save as..." interaction caused for the
     593               "attachment" disposition type), or later on (for instance, when the user decides to save the contents of the current page
     594               being displayed).
     595            </p>
     596            <p id="rfc.section.3.3.p.3">"filename" and "filename*" behave the same, except that "filename*" uses the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.3"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>, allowing the use of characters not present in the ISO-8859-1 character set (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>). When both "filename" and "filename*" are present, a recipient <em class="bcp14">SHOULD</em> pick "filename*" and ignore "filename" - this will make it possible to send the same header value to clients that do not support
     597               "filename*".
     598            </p>
     599            <p id="rfc.section.3.3.p.4">It is essential that user agents treat the specified filename as advisory only, thus be very careful in extracting the desired
     600               information. In particular:
     601            </p>
     602            <ul>
     603               <li>
     604                  <p>When the value contains path separator characters, all but the last segment <em class="bcp14">SHOULD</em> be ignored. This prevents unintentional overwriting of well-known file system location (such as "/etc/passwd").
     605                  </p>
     606               </li>
     607               <li>
     608                  <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
     609                     extension could introduce a privilege escalation when later on the file is opened locally (consider ".exe"). Thus, recipients
     610                     need to ensure that a file extension is used that is safe, optimally matching the media type of the received payload.
     611                  </p>
     612               </li>
     613               <li>
     614                  <p>Other aspects recipients need to be aware of are names that have a special meaning in the filesystem or in shell commands,
     615                     such as "." and "..", "~", "|", and also device names.
     616                  </p>
     617               </li>
     618            </ul>
     619         </div>
     620         <div id="disposition.parameter.extensionsS">
     621            <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#disposition.parameter.extensionsS">Disposition Parameter: Extensions</a></h2>
     622            <p id="rfc.section.3.4.p.1">To enable future extensions, unknown parameters <em class="bcp14">SHOULD</em> be ignored (see also <a href="#RFC2183" id="rfc.xref.RFC2183.3"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>, <a href="https://tools.ietf.org/html/rfc2183#section-2.8">Section 2.8</a>).
     623            </p>
     624         </div>
     625         <div id="extensibility">
     626            <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a href="#extensibility">Extensibility</a></h2>
     627            <p id="rfc.section.3.5.p.1">Note that <a href="https://tools.ietf.org/html/rfc2183#section-9">Section 9</a> of <a href="#RFC2183" id="rfc.xref.RFC2183.4"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a> defines IANA registries both for disposition types and disposition parameters. This registry is shared by different protocols
     628               using Content-Disposition, such as MIME and HTTP. Therefore, not all registered values may make sense in the context of HTTP.
     629            </p>
     630         </div>
     631      </div>
     632      <div>
     633         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;Examples
     634         </h1>
     635         <div id="rfc.figure.u.4"></div>
     636         <p>Direct UA to show "save as" dialog, with a filename of "foo.html":</p><pre class="text">Content-Disposition: Attachment; filename=foo.html
     637</pre><div id="rfc.figure.u.5"></div>
     638         <p>Direct UA to behave as if the Content-Disposition header field wasn't present, but to remember the filename "foo.html" for
     639            a subsequent save operation:
     640         </p><pre class="text">Content-Disposition: INLINE; FILENAME= "foo.html"
     641</pre><div id="rfc.figure.u.6"></div>
     642         <p>Direct UA to show "save as" dialog, with a filename of "an example":</p><pre class="text">Content-Disposition: Attachment; Filename*=UTF-8'<b>en</b>'an<b>%20</b>example
     643</pre><p>Note that this example uses the extended encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.4"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a> to specify that the natural language of the filename is English, and also to encode the space character which is not allowed
     644            in the token production.
     645         </p>
     646         <div id="rfc.figure.u.7"></div>
     647         <p>Direct UA to show "save as" dialog, with a filename containing the Unicode character U+20AC (EURO SIGN):</p><pre class="text">Content-Disposition: attachment; filename*= UTF-8''<b>%e2%82%ac</b>%20rates
     648</pre><p>Here, the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.5"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a> is also used to encode the non-ISO-8859-1 character.
     649         </p>
     650         <div id="rfc.figure.u.8"></div>
     651         <p>Same as above, but adding the "filename" parameter for compatibility with user agents not implementing RFC 5987:</p><pre class="text">Content-Disposition: attachment; filename="EURO rates";
    622652                                 filename*=utf-8''<b>%e2%82%ac</b>%20rates
    623 </pre>  <p>Note: as of August 2010, many user agents unfortunately did not properly handle unexpected parameters, and some that implement
    624          RFC 5987 did not pick the extended parameter when both were present.
    625       </p>
    626       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="i18n" href="#i18n">Internationalization Considerations</a></h1>
    627       <p id="rfc.section.5.p.1">The "filename*" parameter (<a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;3.3</a>), using the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.6"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>, allows the server to transmit characters outside the ISO-8859-1 character set, and also to optionally specify the language
    628          in use.
    629       </p>
    630       <p id="rfc.section.5.p.2">Future parameters might also require internationalization, in which case the same encoding can be used.</p>
    631       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    632       <p id="rfc.section.6.p.1">Using server-supplied information for constructing local filenames introduces many risks. These are summarized in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;3.3</a>.
    633       </p>
    634       <p id="rfc.section.6.p.2">Furthermore, implementers also ought to be aware of the Security Considerations applying to HTTP (see <a href="http://tools.ietf.org/html/rfc2616#section-15">Section 15</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.7"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>), and also the parameter encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.7"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a> (see <a href="#RFC5987" id="rfc.xref.RFC5987.8"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>).
    635       </p>
    636       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="iana.considerations" href="#iana.considerations">IANA Considerations</a></h1>
    637       <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="registry" href="#registry">Registry for Disposition Values and Parameter</a></h2>
    638       <p id="rfc.section.7.1.p.1">This specification does not introduce any changes to the registration procedures for disposition values and parameters that
    639          are defined in <a href="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>.
    640       </p>
    641       <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
    642       <p id="rfc.section.7.2.p.1">This document updates the definition of the Content-Disposition HTTP header field in the permanent HTTP header field registry
    643          (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>).
    644       </p>
    645       <p id="rfc.section.7.2.p.2"> </p>
    646       <dl>
    647          <dt>Header field name:</dt>
    648          <dd>Content-Disposition</dd>
    649          <dt>Applicable protocol:</dt>
    650          <dd>http</dd>
    651          <dt>Status:</dt>
    652          <dd>standard</dd>
    653          <dt>Author/Change controller:</dt>
    654          <dd>IETF</dd>
    655          <dt>Specification document:</dt>
    656          <dd>this specification (<a href="#header.field.definition" id="rfc.xref.header.field.definition.1" title="Header Field Definition">Section&nbsp;3</a>)
    657          </dd>
    658       </dl>
    659       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;Acknowledgements
    660       </h1>
    661       <p id="rfc.section.8.p.1">Thanks to Rolf Eike Beer, Alfred Hoenes, and Roar Lauritzsen for their valuable feedback.</p>
     653</pre><p>Note: as of August 2010, many user agents unfortunately did not properly handle unexpected parameters, and some that implement
     654            RFC 5987 did not pick the extended parameter when both were present.
     655         </p>
     656      </div>
     657      <div id="i18n">
     658         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#i18n">Internationalization Considerations</a></h1>
     659         <p id="rfc.section.5.p.1">The "filename*" parameter (<a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;3.3</a>), using the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.6"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>, allows the server to transmit characters outside the ISO-8859-1 character set, and also to optionally specify the language
     660            in use.
     661         </p>
     662         <p id="rfc.section.5.p.2">Future parameters might also require internationalization, in which case the same encoding can be used.</p>
     663      </div>
     664      <div id="security.considerations">
     665         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     666         <p id="rfc.section.6.p.1">Using server-supplied information for constructing local filenames introduces many risks. These are summarized in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;3.3</a>.
     667         </p>
     668         <p id="rfc.section.6.p.2">Furthermore, implementers also ought to be aware of the Security Considerations applying to HTTP (see <a href="https://tools.ietf.org/html/rfc2616#section-15">Section 15</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.7"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>), and also the parameter encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.7"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a> (see <a href="https://tools.ietf.org/html/rfc5987" id="rfc.xref.RFC5987.8">Appendix ERROR: Anchor 'security.considerations' in RFC5987 not found in source file ''.</a>).
     669         </p>
     670      </div>
     671      <div id="iana.considerations">
     672         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#iana.considerations">IANA Considerations</a></h1>
     673         <div id="registry">
     674            <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a href="#registry">Registry for Disposition Values and Parameter</a></h2>
     675            <p id="rfc.section.7.1.p.1">This specification does not introduce any changes to the registration procedures for disposition values and parameters that
     676               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>.
     677            </p>
     678         </div>
     679         <div id="header.field.registration">
     680            <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
     681            <p id="rfc.section.7.2.p.1">This document updates the definition of the Content-Disposition HTTP header field in the permanent HTTP header field registry
     682               (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>).
     683            </p>
     684            <p id="rfc.section.7.2.p.2"></p>
     685            <dl>
     686               <dt>Header field name:</dt>
     687               <dd>Content-Disposition</dd>
     688               <dt>Applicable protocol:</dt>
     689               <dd>http</dd>
     690               <dt>Status:</dt>
     691               <dd>standard</dd>
     692               <dt>Author/Change controller:</dt>
     693               <dd>IETF</dd>
     694               <dt>Specification document:</dt>
     695               <dd>this specification (<a href="#header.field.definition" id="rfc.xref.header.field.definition.1" title="Header Field Definition">Section&nbsp;3</a>)
     696               </dd>
     697            </dl>
     698         </div>
     699      </div>
     700      <div>
     701         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;Acknowledgements
     702         </h1>
     703         <p id="rfc.section.8.p.1">Thanks to Rolf Eike Beer, Alfred Hoenes, and Roar Lauritzsen for their valuable feedback.</p>
     704      </div>
    662705      <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References
    663706      </h1>
    664707      <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References
    665708      </h2>
    666       <table>       
     709      <table>
    667710         <tr>
    668711            <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td>
     
    671714         <tr>
    672715            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    673             <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.
     716            <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.
    674717            </td>
    675718         </tr>
    676719         <tr>
    677720            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    678             <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.
     721            <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.
    679722            </td>
    680723         </tr>
    681724         <tr>
    682725            <td class="reference"><b id="RFC5987">[RFC5987]</b></td>
    683             <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="http://tools.ietf.org/html/rfc5987">Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers</a>”, RFC&nbsp;5987, August&nbsp;2010.
     726            <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="https://tools.ietf.org/html/rfc5987">Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers</a>”, RFC&nbsp;5987, August&nbsp;2010.
    684727            </td>
    685728         </tr>
     
    687730      <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
    688731      </h2>
    689       <table>             
     732      <table>
    690733         <tr>
    691734            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
    692             <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.
     735            <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.
    693736            </td>
    694737         </tr>
    695738         <tr>
    696739            <td class="reference"><b id="RFC2047">[RFC2047]</b></td>
    697             <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.
     740            <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.
    698741            </td>
    699742         </tr>
    700743         <tr>
    701744            <td class="reference"><b id="RFC2183">[RFC2183]</b></td>
    702             <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.
     745            <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.
    703746            </td>
    704747         </tr>
    705748         <tr>
    706749            <td class="reference"><b id="RFC2231">[RFC2231]</b></td>
    707             <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.
     750            <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.
    708751            </td>
    709752         </tr>
    710753         <tr>
    711754            <td class="reference"><b id="RFC3629">[RFC3629]</b></td>
    712             <td class="top"><a href="mailto:fyergeau@alis.com" title="Alis Technologies">Yergeau, F.</a>, “<a href="http://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>”, RFC&nbsp;3629, STD&nbsp;63, November&nbsp;2003.
     755            <td class="top"><a href="mailto:fyergeau@alis.com" title="Alis Technologies">Yergeau, F.</a>, “<a href="https://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>”, RFC&nbsp;3629, STD&nbsp;63, November&nbsp;2003.
    713756            </td>
    714757         </tr>
    715758         <tr>
    716759            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
    717             <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.
     760            <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.
    718761            </td>
    719762         </tr>
    720763         <tr>
    721764            <td class="reference"><b id="RFC3986">[RFC3986]</b></td>
    722             <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>”, RFC&nbsp;3986, STD&nbsp;66, January&nbsp;2005.
     765            <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>”, RFC&nbsp;3986, STD&nbsp;66, January&nbsp;2005.
    723766            </td>
    724767         </tr>
    725768      </table>
    726       <div class="avoidbreak">
    727          <h1 id="rfc.authors"><a href="#rfc.authors">Author's Address</a></h1>
    728          <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span><span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline">Email: <a href="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>
    729       </div>
    730       <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="changes.from.rfc2616" href="#changes.from.rfc2616">Changes from the RFC 2616 Definition</a></h1>
    731       <p id="rfc.section.A.p.1">Compared to <a href="http://tools.ietf.org/html/rfc2616#section-19.5.1">Section 19.5.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.8"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, the following normative changes reflecting actual implementations have been made:
    732       </p>
    733       <ul>
    734          <li>According to RFC 2616, the disposition type "attachment" only applies to content of type "application/octet-stream". This
    735             restriction has been removed, because user agents in practice do not check the content type, and it also discourages properly
    736             declaring the media type.
    737          </li>
    738          <li>RFC 2616 only allows "quoted-string" for the filename parameter. This would be an exceptional parameter syntax, and also doesn't
    739             reflect actual use.
    740          </li>
    741          <li>The definition for the disposition type "inline" (<a href="#RFC2183" id="rfc.xref.RFC2183.6"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>, <a href="http://tools.ietf.org/html/rfc2183#section-2.1">Section 2.1</a>) has been re-added with a suggestion for its processing.
    742          </li>
    743          <li>This specification requires support for the extended parameter encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.9"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>.
    744          </li>
    745       </ul>
    746       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="diffs.compared.to.rfc2183" href="#diffs.compared.to.rfc2183">Differences compared to RFC 2183</a></h1>
    747       <p id="rfc.section.B.p.1"> <a href="http://tools.ietf.org/html/rfc2183#section-2">Section 2</a> of <a href="#RFC2183" id="rfc.xref.RFC2183.7"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a> defines several additional disposition parameters: "creation-date", "modification-date", "quoted-date-time", and "size". These
    748          do not appear to be implemented by any user agent, thus have been omitted from this specification.
    749       </p>
    750       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="alternatives" href="#alternatives">Alternative Approaches to Internationalization</a></h1>
    751       <p id="rfc.section.C.p.1">By default, HTTP header field parameters cannot carry characters outside the ISO-8859-1 (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.2"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>) character encoding (see <a href="#RFC2616" id="rfc.xref.RFC2616.9"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>). For the "filename" parameter, this of course is an unacceptable restriction.
    752       </p>
    753       <p id="rfc.section.C.p.2">Unfortunately, user agent implementers have not managed to come up with an interoperable approach, although the IETF Standards
    754          Track specifies exactly one solution (<a href="#RFC2231" id="rfc.xref.RFC2231.1"><cite title="MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations">[RFC2231]</cite></a>, clarified and profiled for HTTP in <a href="#RFC5987" id="rfc.xref.RFC5987.10"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>).
    755       </p>
    756       <p id="rfc.section.C.p.3">For completeness, the sections below describe the various approaches that have been tried, and explains how they are inferior
    757          to the RFC 5987 encoding used in this specification.
    758       </p>
    759       <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;<a id="alternatives.rfc2047" href="#alternatives.rfc2047">RFC 2047 Encoding</a></h2>
    760       <p id="rfc.section.C.1.p.1">RFC 2047 defines an encoding mechanism for header fields, but this encoding is not supposed to be used for header field parameters
    761          - see <a href="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>:
    762       </p>
    763       <blockquote id="rfc.section.C.1.p.2" cite="http://tools.ietf.org/html/rfc2047#section-5">
    764          <p>An 'encoded-word' MUST NOT appear within a 'quoted-string'.</p> 
    765          <p>...</p> 
    766          <p>An 'encoded-word' MUST NOT be used in parameter of a MIME Content-Type or Content-Disposition field, or in any structured
    767             field body except within a 'comment' or 'phrase'.
    768          </p>
    769       </blockquote>
    770       <p id="rfc.section.C.1.p.3">In practice, some user agents implement the encoding, some do not (exposing the encoded string to the user), and some get
    771          confused by it.
    772       </p>
    773       <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;<a id="alternatives.percent" href="#alternatives.percent">Percent Encoding</a></h2>
    774       <p id="rfc.section.C.2.p.1">Some user agents accept percent encoded (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>) sequences of characters encoded using the UTF-8 (<a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a>) character encoding.
    775       </p>
    776       <p id="rfc.section.C.2.p.2">In practice, this is hard to use because those user agents that do not support it will display the escaped character sequence
    777          to the user.
    778       </p>
    779       <p id="rfc.section.C.2.p.3">Furthermore, the first user agent to implement this did choose the encoding based on local settings; thus making it very hard
    780          to use in multi-lingual environments.
    781       </p>
    782       <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;<a id="alternatives.sniff" href="#alternatives.sniff">Encoding Sniffing</a></h2>
    783       <p id="rfc.section.C.3.p.1">Some user agents inspect the value (which defaults to ISO-8859-1) and switch to UTF-8 when it seems to be more likely to be
    784          the correct interpretation.
    785       </p>
    786       <p id="rfc.section.C.3.p.2">As with the approaches above, this is not interoperable and furthermore risks misinterpreting the actual value.</p>
    787       <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a id="alternatives.implementations" href="#alternatives.implementations">Implementations</a></h2>
    788       <p id="rfc.section.C.4.p.1">Unfortunately, as of August 2010, neither the encoding defined in RFCs 2231 and 5789, nor any of the alternate approaches
    789          discussed above was implemented interoperably. Thus, this specification recommends the approach defined in RFC 5987, which
    790          at least has the advantage of actually being specified properly.
    791       </p>
    792       <p id="rfc.section.C.4.p.2">The table below shows the implementation support for the various approaches: <span class="comment" id="impls">[<a href="#impls" class="smpl">impls</a>: Discuss: should we mention the implementation status of actual UAs in a RFC? Up to the IESG to decide...]</span>
    793       </p>
    794       <div id="rfc.table.u.1">
    795          <table class="tt full left" cellpadding="3" cellspacing="0">
    796             <thead>
    797                <tr>
    798                   <th>User Agent</th>
    799                   <th>RFC 2231/5987</th>
    800                   <th>RFC 2047</th>
    801                   <th>Percent Encoding</th>
    802                   <th>Encoding Sniffing</th>
    803                </tr>
    804             </thead>
    805             <tbody>
    806                <tr>
    807                   <td class="left">Chrome</td>
    808                   <td class="left">no</td>
    809                   <td class="left">yes</td>
    810                   <td class="left">yes</td>
    811                   <td class="left">yes</td>
    812                </tr>
    813                <tr>
    814                   <td class="left">Firefox</td>
    815                   <td class="left">yes (*)</td>
    816                   <td class="left">yes</td>
    817                   <td class="left">no</td>
    818                   <td class="left">yes</td>
    819                </tr>
    820                <tr>
    821                   <td class="left">Internet Explorer</td>
    822                   <td class="left">no</td>
    823                   <td class="left">no</td>
    824                   <td class="left">yes</td>
    825                   <td class="left">no</td>
    826                </tr>
    827                <tr>
    828                   <td class="left">Konqueror</td>
    829                   <td class="left">yes</td>
    830                   <td class="left">no</td>
    831                   <td class="left">no</td>
    832                   <td class="left">no</td>
    833                </tr>
    834                <tr>
    835                   <td class="left">Opera</td>
    836                   <td class="left">yes (*)</td>
    837                   <td class="left">no</td>
    838                   <td class="left">no</td>
    839                   <td class="left">no</td>
    840                </tr>
    841                <tr>
    842                   <td class="left">Safari</td>
    843                   <td class="left">no</td>
    844                   <td class="left">no</td>
    845                   <td class="left">no</td>
    846                   <td class="left">yes</td>
    847                </tr>
    848             </tbody>
    849          </table>
    850          <p>(*) Does not implement the fallback behavior to "filename" described in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;3.3</a>.
    851          </p>
    852       </div>
    853       <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    854       <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since draft-reschke-rfc2183-in-http-00
    855       </h2>
    856       <p id="rfc.section.D.1.p.1">Adjust terminology ("header" -&gt; "header field"). Update rfc2231-in-http reference.</p>
    857       <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-reschke-rfc2183-in-http-01
    858       </h2>
    859       <p id="rfc.section.D.2.p.1">Update rfc2231-in-http reference. Actually define the "filename" parameter. Add internationalization considerations. Add examples
    860          using the RFC 5987 encoding. Add overview over other approaches, plus a table reporting implementation status. Add and resolve
    861          issue "nodep2183". Add issues "asciivsiso", "deplboth", "quoted", and "registry".
    862       </p>
    863       <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-reschke-rfc2183-in-http-02
    864       </h2>
    865       <p id="rfc.section.D.3.p.1">Add and close issue "docfallback". Close issues "asciivsiso", "deplboth", "quoted", and "registry".</p>
    866       <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a>&nbsp;Since draft-reschke-rfc2183-in-http-03
    867       </h2>
    868       <p id="rfc.section.D.4.p.1">Updated to be a Working Draft of the IETF HTTPbis Working Group.</p>
     769      <div id="changes.from.rfc2616">
     770         <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>
     771         <p id="rfc.section.A.p.1">Compared to <a href="https://tools.ietf.org/html/rfc2616#section-19.5.1">Section 19.5.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.8"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, the following normative changes reflecting actual implementations have been made:
     772         </p>
     773         <ul>
     774            <li>According to RFC 2616, the disposition type "attachment" only applies to content of type "application/octet-stream". This
     775               restriction has been removed, because user agents in practice do not check the content type, and it also discourages properly
     776               declaring the media type.
     777            </li>
     778            <li>RFC 2616 only allows "quoted-string" for the filename parameter. This would be an exceptional parameter syntax, and also doesn't
     779               reflect actual use.
     780            </li>
     781            <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.
     782            </li>
     783            <li>This specification requires support for the extended parameter encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.9"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>.
     784            </li>
     785         </ul>
     786      </div>
     787      <div id="diffs.compared.to.rfc2183">
     788         <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>
     789         <p id="rfc.section.B.p.1"><a href="https://tools.ietf.org/html/rfc2183#section-2">Section 2</a> of <a href="#RFC2183" id="rfc.xref.RFC2183.7"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a> defines several additional disposition parameters: "creation-date", "modification-date", "quoted-date-time", and "size". These
     790            do not appear to be implemented by any user agent, thus have been omitted from this specification.
     791         </p>
     792      </div>
     793      <div id="alternatives">
     794         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#alternatives">Alternative Approaches to Internationalization</a></h1>
     795         <p id="rfc.section.C.p.1">By default, HTTP header field parameters cannot carry characters outside the ISO-8859-1 (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.2"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>) character encoding (see <a href="#RFC2616" id="rfc.xref.RFC2616.9"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="https://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>). For the "filename" parameter, this of course is an unacceptable restriction.
     796         </p>
     797         <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
     798            Track specifies exactly one solution (<a href="#RFC2231" id="rfc.xref.RFC2231.1"><cite title="MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations">[RFC2231]</cite></a>, clarified and profiled for HTTP in <a href="#RFC5987" id="rfc.xref.RFC5987.10"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>).
     799         </p>
     800         <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
     801            to the RFC 5987 encoding used in this specification.
     802         </p>
     803         <div id="alternatives.rfc2047">
     804            <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>
     805            <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
     806               - 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>:
     807            </p>
     808            <blockquote id="rfc.section.C.1.p.2" cite="http://tools.ietf.org/html/rfc2047#section-5">
     809               <p>An 'encoded-word' MUST NOT appear within a 'quoted-string'.</p>
     810               <p>...</p>
     811               <p>An 'encoded-word' MUST NOT be used in parameter of a MIME Content-Type or Content-Disposition field, or in any structured
     812                  field body except within a 'comment' or 'phrase'.
     813               </p>
     814            </blockquote>
     815            <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
     816               confused by it.
     817            </p>
     818         </div>
     819         <div id="alternatives.percent">
     820            <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;<a href="#alternatives.percent">Percent Encoding</a></h2>
     821            <p id="rfc.section.C.2.p.1">Some user agents accept percent encoded (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="https://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>) sequences of characters encoded using the UTF-8 (<a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a>) character encoding.
     822            </p>
     823            <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
     824               to the user.
     825            </p>
     826            <p id="rfc.section.C.2.p.3">Furthermore, the first user agent to implement this did choose the encoding based on local settings; thus making it very hard
     827               to use in multi-lingual environments.
     828            </p>
     829         </div>
     830         <div id="alternatives.sniff">
     831            <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;<a href="#alternatives.sniff">Encoding Sniffing</a></h2>
     832            <p id="rfc.section.C.3.p.1">Some user agents inspect the value (which defaults to ISO-8859-1) and switch to UTF-8 when it seems to be more likely to be
     833               the correct interpretation.
     834            </p>
     835            <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>
     836         </div>
     837         <div id="alternatives.implementations">
     838            <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a href="#alternatives.implementations">Implementations</a></h2>
     839            <p id="rfc.section.C.4.p.1">Unfortunately, as of August 2010, neither the encoding defined in RFCs 2231 and 5789, nor any of the alternate approaches
     840               discussed above was implemented interoperably. Thus, this specification recommends the approach defined in RFC 5987, which
     841               at least has the advantage of actually being specified properly.
     842            </p>
     843            <p id="rfc.section.C.4.p.2">The table below shows the implementation support for the various approaches: <span class="comment" id="impls">[<a href="#impls" class="smpl">impls</a>: Discuss: should we mention the implementation status of actual UAs in a RFC? Up to the IESG to decide...]</span>
     844            </p>
     845            <div id="rfc.table.u.1">
     846               <table class="tt full left" cellpadding="3" cellspacing="0">
     847                  <thead>
     848                     <tr>
     849                        <th>User Agent</th>
     850                        <th>RFC 2231/5987</th>
     851                        <th>RFC 2047</th>
     852                        <th>Percent Encoding</th>
     853                        <th>Encoding Sniffing</th>
     854                     </tr>
     855                  </thead>
     856                  <tbody>
     857                     <tr>
     858                        <td class="left">Chrome</td>
     859                        <td class="left">no</td>
     860                        <td class="left">yes</td>
     861                        <td class="left">yes</td>
     862                        <td class="left">yes</td>
     863                     </tr>
     864                     <tr>
     865                        <td class="left">Firefox</td>
     866                        <td class="left">yes (*)</td>
     867                        <td class="left">yes</td>
     868                        <td class="left">no</td>
     869                        <td class="left">yes</td>
     870                     </tr>
     871                     <tr>
     872                        <td class="left">Internet Explorer</td>
     873                        <td class="left">no</td>
     874                        <td class="left">no</td>
     875                        <td class="left">yes</td>
     876                        <td class="left">no</td>
     877                     </tr>
     878                     <tr>
     879                        <td class="left">Konqueror</td>
     880                        <td class="left">yes</td>
     881                        <td class="left">no</td>
     882                        <td class="left">no</td>
     883                        <td class="left">no</td>
     884                     </tr>
     885                     <tr>
     886                        <td class="left">Opera</td>
     887                        <td class="left">yes (*)</td>
     888                        <td class="left">no</td>
     889                        <td class="left">no</td>
     890                        <td class="left">no</td>
     891                     </tr>
     892                     <tr>
     893                        <td class="left">Safari</td>
     894                        <td class="left">no</td>
     895                        <td class="left">no</td>
     896                        <td class="left">no</td>
     897                        <td class="left">yes</td>
     898                     </tr>
     899                  </tbody>
     900               </table>
     901               <p>(*) Does not implement the fallback behavior to "filename" described in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;3.3</a>.
     902               </p>
     903            </div>
     904         </div>
     905      </div>
     906      <div id="change.log">
     907         <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
     908         <div>
     909            <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since draft-reschke-rfc2183-in-http-00
     910            </h2>
     911            <p id="rfc.section.D.1.p.1">Adjust terminology ("header" -&gt; "header field"). Update rfc2231-in-http reference.</p>
     912         </div>
     913         <div>
     914            <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-reschke-rfc2183-in-http-01
     915            </h2>
     916            <p id="rfc.section.D.2.p.1">Update rfc2231-in-http reference. Actually define the "filename" parameter. Add internationalization considerations. Add examples
     917               using the RFC 5987 encoding. Add overview over other approaches, plus a table reporting implementation status. Add and resolve
     918               issue "nodep2183". Add issues "asciivsiso", "deplboth", "quoted", and "registry".
     919            </p>
     920         </div>
     921         <div>
     922            <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-reschke-rfc2183-in-http-02
     923            </h2>
     924            <p id="rfc.section.D.3.p.1">Add and close issue "docfallback". Close issues "asciivsiso", "deplboth", "quoted", and "registry".</p>
     925         </div>
     926         <div>
     927            <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a>&nbsp;Since draft-reschke-rfc2183-in-http-03
     928            </h2>
     929            <p id="rfc.section.D.4.p.1">Updated to be a Working Draft of the IETF HTTPbis Working Group.</p>
     930         </div>
     931      </div>
    869932      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    870933      <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>
     
    872935      <div class="print2col">
    873936         <ul class="ind">
    874             <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">
    875                   <li class="indline1">Content-Disposition header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.1"><b>3</b></a>, <a class="iref" href="#rfc.xref.header.field.definition.1">7.2</a></li>
     937            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
     938                  <li>Content-Disposition header&nbsp;&nbsp;<a href="#rfc.iref.c.1"><b>3</b></a>, <a href="#rfc.xref.header.field.definition.1">7.2</a></li>
    876939               </ul>
    877940            </li>
    878             <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">
    879                   <li class="indline1">Headers&nbsp;&nbsp;
    880                      <ul class="ind">
    881                         <li class="indline1">Content-Disposition&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.1"><b>3</b></a>, <a class="iref" href="#rfc.xref.header.field.definition.1">7.2</a></li>
     941            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
     942                  <li>Headers&nbsp;&nbsp;
     943                     <ul>
     944                        <li>Content-Disposition&nbsp;&nbsp;<a href="#rfc.iref.h.1"><b>3</b></a>, <a href="#rfc.xref.header.field.definition.1">7.2</a></li>
    882945                     </ul>
    883946                  </li>
    884947               </ul>
    885948            </li>
    886             <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">
    887                   <li class="indline1"><em>ISO-8859-1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.ISO-8859-1.1">3.3</a>, <a class="iref" href="#ISO-8859-1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.ISO-8859-1.2">C</a></li>
     949            <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul>
     950                  <li><em>ISO-8859-1</em>&nbsp;&nbsp;<a href="#rfc.xref.ISO-8859-1.1">3.3</a>, <a href="#ISO-8859-1"><b>9.1</b></a>, <a href="#rfc.xref.ISO-8859-1.2">C</a></li>
    888951               </ul>
    889952            </li>
    890             <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    891                   <li class="indline1"><em>RFC2046</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2046.1">3.3</a>, <a class="iref" href="#RFC2046"><b>9.2</b></a></li>
    892                   <li class="indline1"><em>RFC2047</em>&nbsp;&nbsp;<a class="iref" href="#RFC2047"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2047.1">C.1</a><ul class="ind">
    893                         <li class="indline1"><em>Section 5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2047.1">C.1</a></li>
     953            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
     954                  <li><em>RFC2046</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">3.3</a>, <a href="#RFC2046"><b>9.2</b></a></li>
     955                  <li><em>RFC2047</em>&nbsp;&nbsp;<a href="#RFC2047"><b>9.2</b></a>, <a href="#rfc.xref.RFC2047.1">C.1</a><ul>
     956                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2047.1">C.1</a></li>
    894957                     </ul>
    895958                  </li>
    896                   <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">2</a>, <a class="iref" href="#RFC2119"><b>9.1</b></a></li>
    897                   <li class="indline1"><em>RFC2183</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2183.1">1</a>, <a class="iref" href="#rfc.xref.RFC2183.2">3.2</a>, <a class="iref" href="#rfc.xref.RFC2183.3">3.4</a>, <a class="iref" href="#rfc.xref.RFC2183.4">3.5</a>, <a class="iref" href="#rfc.xref.RFC2183.5">7.1</a>, <a class="iref" href="#RFC2183"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2183.6">A</a>, <a class="iref" href="#rfc.xref.RFC2183.7">B</a><ul class="ind">
    898                         <li class="indline1"><em>Section 2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2183.7">B</a></li>
    899                         <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2183.6">A</a></li>
    900                         <li class="indline1"><em>Section 2.8</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2183.2">3.2</a>, <a class="iref" href="#rfc.xref.RFC2183.3">3.4</a></li>
    901                         <li class="indline1"><em>Section 9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2183.4">3.5</a>, <a class="iref" href="#rfc.xref.RFC2183.5">7.1</a></li>
     959                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">2</a>, <a href="#RFC2119"><b>9.1</b></a></li>
     960                  <li><em>RFC2183</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2183.1">1</a>, <a href="#rfc.xref.RFC2183.2">3.2</a>, <a href="#rfc.xref.RFC2183.3">3.4</a>, <a href="#rfc.xref.RFC2183.4">3.5</a>, <a href="#rfc.xref.RFC2183.5">7.1</a>, <a href="#RFC2183"><b>9.2</b></a>, <a href="#rfc.xref.RFC2183.6">A</a>, <a href="#rfc.xref.RFC2183.7">B</a><ul>
     961                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2183.7">B</a></li>
     962                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2183.6">A</a></li>
     963                        <li><em>Section 2.8</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2183.2">3.2</a>, <a href="#rfc.xref.RFC2183.3">3.4</a></li>
     964                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2183.4">3.5</a>, <a href="#rfc.xref.RFC2183.5">7.1</a></li>
    902965                     </ul>
    903966                  </li>
    904                   <li class="indline1"><em>RFC2231</em>&nbsp;&nbsp;<a class="iref" href="#RFC2231"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2231.1">C</a></li>
    905                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#rfc.xref.RFC2616.3">2</a>, <a class="iref" href="#rfc.xref.RFC2616.4">3.1</a>, <a class="iref" href="#rfc.xref.RFC2616.5">3.1</a>, <a class="iref" href="#rfc.xref.RFC2616.6">3.1</a>, <a class="iref" href="#rfc.xref.RFC2616.7">6</a>, <a class="iref" href="#RFC2616"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC2616.8">A</a>, <a class="iref" href="#rfc.xref.RFC2616.9">C</a><ul class="ind">
    906                         <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.3">2</a></li>
    907                         <li class="indline1"><em>Section 2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.5">3.1</a>, <a class="iref" href="#rfc.xref.RFC2616.9">C</a></li>
    908                         <li class="indline1"><em>Section 3.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.6">3.1</a></li>
    909                         <li class="indline1"><em>Section 15.5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.2">1</a></li>
    910                         <li class="indline1"><em>Section 15</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.7">6</a></li>
    911                         <li class="indline1"><em>Section 19.5.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.8">A</a></li>
     967                  <li><em>RFC2231</em>&nbsp;&nbsp;<a href="#RFC2231"><b>9.2</b></a>, <a href="#rfc.xref.RFC2231.1">C</a></li>
     968                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">1</a>, <a href="#rfc.xref.RFC2616.3">2</a>, <a href="#rfc.xref.RFC2616.4">3.1</a>, <a href="#rfc.xref.RFC2616.5">3.1</a>, <a href="#rfc.xref.RFC2616.6">3.1</a>, <a href="#rfc.xref.RFC2616.7">6</a>, <a href="#RFC2616"><b>9.1</b></a>, <a href="#rfc.xref.RFC2616.8">A</a>, <a href="#rfc.xref.RFC2616.9">C</a><ul>
     969                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.3">2</a></li>
     970                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.5">3.1</a>, <a href="#rfc.xref.RFC2616.9">C</a></li>
     971                        <li><em>Section 3.6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.6">3.1</a></li>
     972                        <li><em>Section 15.5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.2">1</a></li>
     973                        <li><em>Section 15</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.7">6</a></li>
     974                        <li><em>Section 19.5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.8">A</a></li>
    912975                     </ul>
    913976                  </li>
    914                   <li class="indline1"><em>RFC3629</em>&nbsp;&nbsp;<a class="iref" href="#RFC3629"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC3629.1">C.2</a></li>
    915                   <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">7.2</a>, <a class="iref" href="#RFC3864"><b>9.2</b></a></li>
    916                   <li class="indline1"><em>RFC3986</em>&nbsp;&nbsp;<a class="iref" href="#RFC3986"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC3986.1">C.2</a><ul class="ind">
    917                         <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3986.1">C.2</a></li>
     977                  <li><em>RFC3629</em>&nbsp;&nbsp;<a href="#RFC3629"><b>9.2</b></a>, <a href="#rfc.xref.RFC3629.1">C.2</a></li>
     978                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">7.2</a>, <a href="#RFC3864"><b>9.2</b></a></li>
     979                  <li><em>RFC3986</em>&nbsp;&nbsp;<a href="#RFC3986"><b>9.2</b></a>, <a href="#rfc.xref.RFC3986.1">C.2</a><ul>
     980                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.1">C.2</a></li>
    918981                     </ul>
    919982                  </li>
    920                   <li class="indline1"><em>RFC5987</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5987.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC5987.2">3.1</a>, <a class="iref" href="#rfc.xref.RFC5987.3">3.3</a>, <a class="iref" href="#rfc.xref.RFC5987.4">4</a>, <a class="iref" href="#rfc.xref.RFC5987.5">4</a>, <a class="iref" href="#rfc.xref.RFC5987.6">5</a>, <a class="iref" href="#rfc.xref.RFC5987.7">6</a>, <a class="iref" href="#rfc.xref.RFC5987.8">6</a>, <a class="iref" href="#RFC5987"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC5987.9">A</a>, <a class="iref" href="#rfc.xref.RFC5987.10">C</a><ul class="ind">
    921                         <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5987.2">3.1</a></li>
     983                  <li><em>RFC5987</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.1">3.1</a>, <a href="#rfc.xref.RFC5987.2">3.1</a>, <a href="#rfc.xref.RFC5987.3">3.3</a>, <a href="#rfc.xref.RFC5987.4">4</a>, <a href="#rfc.xref.RFC5987.5">4</a>, <a href="#rfc.xref.RFC5987.6">5</a>, <a href="#rfc.xref.RFC5987.7">6</a>, <a href="#rfc.xref.RFC5987.8">6</a>, <a href="#RFC5987"><b>9.1</b></a>, <a href="#rfc.xref.RFC5987.9">A</a>, <a href="#rfc.xref.RFC5987.10">C</a><ul>
     984                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.2">3.1</a></li>
    922985                     </ul>
    923986                  </li>
     
    926989         </ul>
    927990      </div>
     991      <div class="avoidbreak">
     992         <h1 id="rfc.authors"><a href="#rfc.authors">Author's Address</a></h1>
     993         <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>
     994      </div>
    928995   </body>
    929996</html>
Note: See TracChangeset for help on using the changeset viewer.