Ignore:
Timestamp:
May 27, 2011, 2:29:57 AM (9 years ago)
Author:
julian.reschke@…
Message:

apply RFC-Editor AUTH48 changes

Location:
draft-ietf-httpbis-content-disp/latest
Files:
2 edited

Legend:

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

    r1293 r1294  
    138138  margin-left: 2em;
    139139}
    140 table.tt {
    141   vertical-align: top;
    142 }
    143 table.full {
    144   border-style: outset;
    145   border-width: 1px;
    146 }
    147 table.headers {
    148   border-style: outset;
    149   border-width: 1px;
    150 }
    151 table.tt td {
    152   vertical-align: top;
    153 }
    154 table.full td {
    155   border-style: inset;
    156   border-width: 1px;
    157 }
    158 table.tt th {
    159   vertical-align: top;
    160 }
    161 table.full th {
    162   border-style: inset;
    163   border-width: 1px;
    164 }
    165 table.headers th {
    166   border-style: none none inset none;
    167   border-width: 1px;
    168 }
    169 table.left {
    170   margin-right: auto;
    171 }
    172 table.right {
    173   margin-left: auto;
    174 }
    175 table.center {
    176   margin-left: auto;
    177   margin-right: auto;
    178 }
    179 caption {
    180   caption-side: bottom;
    181   font-weight: bold;
    182   font-size: 9pt;
    183   margin-top: .5em;
    184 }
    185 
    186140table.header {
    187141  border-spacing: 1px;
     
    407361      <link rel="Appendix" title="C Alternative Approaches to Internationalization" href="#rfc.section.C">
    408362      <link rel="Appendix" title="D Advice on Generating Content-Disposition Header Fields" href="#rfc.section.D">
    409       <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E">
    410363      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.547, 2011-04-17 09:42:41, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    411364      <link rel="schema.dct" href="http://purl.org/dc/terms/">
     
    448401         aspects.
    449402      </p>
    450       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor before publication)</a></h1>
    451       <p>This specification is expected to replace the definition of Content-Disposition in the HTTP/1.1 specification, as currently
    452          revised by the IETF HTTPbis working group. See also &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/123">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/123</a>&gt;.
    453       </p> 
    454       <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    455          list is at &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/query?component=content-disp">http://trac.tools.ietf.org/wg/httpbis/trac/query?component=content-disp</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
    456       </p> 
    457       <p>The changes in this draft are summarized in <a href="#changes.since.09" title="Since draft-ietf-httpbis-content-disp-09">Appendix&nbsp;E.14</a>.
    458       </p>
    459403      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
    460404      <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
     
    509453               <li>C.2&nbsp;&nbsp;&nbsp;<a href="#alternatives.percent">Percent Encoding</a></li>
    510454               <li>C.3&nbsp;&nbsp;&nbsp;<a href="#alternatives.sniff">Encoding Sniffing</a></li>
    511                <li>C.4&nbsp;&nbsp;&nbsp;<a href="#alternatives.implementations">Implementations (to be removed by RFC Editor before publication)</a></li>
    512455            </ul>
    513456         </li>
    514457         <li>D.&nbsp;&nbsp;&nbsp;<a href="#advice.generating">Advice on Generating Content-Disposition Header Fields</a></li>
    515          <li>E.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
    516                <li>E.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.1">Since draft-reschke-rfc2183-in-http-00</a></li>
    517                <li>E.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.2">Since draft-reschke-rfc2183-in-http-01</a></li>
    518                <li>E.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.3">Since draft-reschke-rfc2183-in-http-02</a></li>
    519                <li>E.4&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.4">Since draft-reschke-rfc2183-in-http-03</a></li>
    520                <li>E.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.00">Since draft-ietf-httpbis-content-disp-00</a></li>
    521                <li>E.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.01">Since draft-ietf-httpbis-content-disp-01</a></li>
    522                <li>E.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-content-disp-02</a></li>
    523                <li>E.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-content-disp-03</a></li>
    524                <li>E.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-content-disp-04</a></li>
    525                <li>E.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-content-disp-05</a></li>
    526                <li>E.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-content-disp-06</a></li>
    527                <li>E.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-content-disp-07</a></li>
    528                <li>E.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-content-disp-08</a></li>
    529                <li>E.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-content-disp-09</a></li>
    530             </ul>
    531          </li>
    532458         <li><a href="#rfc.index">Index</a></li>
    533459      </ul>
     
    624550         being displayed).
    625551      </p>
    626       <p id="rfc.section.4.3.p.3">The parameters "filename" and "filename*" differ only in that "filename*" uses the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.3"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>, allowing the use of characters not present in the ISO-8859-1 character set (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>).
     552      <p id="rfc.section.4.3.p.3">The parameters "filename" and "filename*" differ only in that "filename*" uses the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.3"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>, allowing the use of characters not present in the ISO-8859-1 character set (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No.&nbsp;1">[ISO-8859-1]</cite></a>).
    627553      </p>
    628554      <p id="rfc.section.4.3.p.4">Many user agent implementations predating this specification do not understand the "filename*" parameter. Therefore, when
     
    678604         for a subsequent save operation:
    679605      </p>  <pre class="text">Content-Disposition: INLINE; FILENAME= "an example.html"
    680 </pre>  <p>Note: this uses the quoted-string form so that the space character can be included.</p>
     606</pre>  <p>Note: This uses the quoted-string form so that the space character can be included.</p>
    681607      <div id="rfc.figure.u.6"></div>
    682608      <p>Direct the UA to show "save as" dialog, with a filename containing the Unicode character U+20AC (EURO SIGN):</p>  <pre class="text">Content-Disposition: attachment;
     
    690616                     filename="EURO rates";
    691617                     filename*=utf-8''<b>%e2%82%ac</b>%20rates
    692 </pre>  <p>Note: those user agents that do not support the RFC 5987 encoding ignore "filename*" when it occurs after "filename".</p>
     618</pre>  <p>Note: Those user agents that do not support the RFC 5987 encoding ignore "filename*" when it occurs after "filename".</p>
    693619      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="i18n" href="#i18n">Internationalization Considerations</a></h1>
    694620      <p id="rfc.section.6.p.1">The "filename*" parameter (<a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;4.3</a>), using the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.5"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>, allows the server to transmit characters outside the ISO-8859-1 character set, and also to optionally specify the language
     
    738664         <tr>
    739665            <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td>
    740             <td class="top">International Organization for Standardization, “Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1”, ISO/IEC&nbsp;8859-1:1998, 1998.</td>
     666            <td class="top">International Organization for Standardization, “Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No.&nbsp;1”, ISO/IEC&nbsp;8859-1:1998, 1998.</td>
    741667         </tr>
    742668         <tr>
     
    824750      </p>
    825751      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="alternatives" href="#alternatives">Alternative Approaches to Internationalization</a></h1>
    826       <p id="rfc.section.C.p.1">By default, HTTP header field parameters cannot carry characters outside the ISO-8859-1 (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.2"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>) character encoding (see <a href="#RFC2616" id="rfc.xref.RFC2616.11"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>). For the "filename" parameter, this of course is an unacceptable restriction.
     752      <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.&nbsp;1">[ISO-8859-1]</cite></a>) character encoding (see <a href="#RFC2616" id="rfc.xref.RFC2616.11"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-2.2">Section 2.2</a>). For the "filename" parameter, this of course is an unacceptable restriction.
    827753      </p>
    828754      <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
     
    859785      </p>
    860786      <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>
    861       <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a id="alternatives.implementations" href="#alternatives.implementations">Implementations (to be removed by RFC Editor before publication)</a></h2>
    862       <p id="rfc.section.C.4.p.1">Unfortunately, as of March 2011, neither the encoding defined in RFCs 2231 and 5987, nor any of the alternate approaches discussed
    863          above was implemented interoperably. Thus, this specification recommends the approach defined in RFC 5987, which at least
    864          has the advantage of actually being specified properly.
    865       </p>
    866       <p id="rfc.section.C.4.p.2">The table below shows the support for the various approaches in the current implementations:</p>
    867       <div id="rfc.table.u.1">
    868          <table class="tt full left" cellpadding="3" cellspacing="0">
    869             <thead>
    870                <tr>
    871                   <th>User Agent</th>
    872                   <th>RFC 2231/5987</th>
    873                   <th>RFC 2047</th>
    874                   <th>Percent Encoding</th>
    875                   <th>Encoding Sniffing</th>
    876                </tr>
    877             </thead>
    878             <tbody>
    879                <tr>
    880                   <td class="left">Chrome</td>
    881                   <td class="left">yes</td>
    882                   <td class="left">yes</td>
    883                   <td class="left">yes</td>
    884                   <td class="left">yes</td>
    885                </tr>
    886                <tr>
    887                   <td class="left">Firefox</td>
    888                   <td class="left">yes (*)</td>
    889                   <td class="left">yes</td>
    890                   <td class="left">no</td>
    891                   <td class="left">yes</td>
    892                </tr>
    893                <tr>
    894                   <td class="left">Internet Explorer</td>
    895                   <td class="left">yes (**)</td>
    896                   <td class="left">no</td>
    897                   <td class="left">yes</td>
    898                   <td class="left">no</td>
    899                </tr>
    900                <tr>
    901                   <td class="left">Konqueror</td>
    902                   <td class="left">yes</td>
    903                   <td class="left">no</td>
    904                   <td class="left">no</td>
    905                   <td class="left">no</td>
    906                </tr>
    907                <tr>
    908                   <td class="left">Opera</td>
    909                   <td class="left">yes</td>
    910                   <td class="left">no</td>
    911                   <td class="left">no</td>
    912                   <td class="left">no</td>
    913                </tr>
    914                <tr>
    915                   <td class="left">Safari</td>
    916                   <td class="left">no</td>
    917                   <td class="left">no</td>
    918                   <td class="left">no</td>
    919                   <td class="left">yes</td>
    920                </tr>
    921             </tbody>
    922          </table>
    923       </div>
    924       <p id="rfc.section.C.4.p.3">(*) Does not implement the fallback behavior to "filename" described in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;4.3</a>; a fix is planned for Firefox 5.
    925       </p>
    926       <p id="rfc.section.C.4.p.4">(**) Starting with Internet Explorer 9, but only implements UTF-8.</p>
    927787      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="advice.generating" href="#advice.generating">Advice on Generating Content-Disposition Header Fields</a></h1>
    928788      <p id="rfc.section.D.p.1">To successfully interoperate with existing and future user agents, senders of the Content-Disposition header field are advised
     
    942802            user agents, and "\" can be considered an illegal path character.
    943803         </li>
    944          <li>Avoid using non-ASCII characters in the filename parameter. Although most existing implementations will decode them as ISO-8859-1,
     804         <li>Avoid using non-ASCII characters in the filename parameter. Although most existing implementations will decode them as ISO‑8859‑1,
    945805            some will apply heuristics to detect UTF-8, and thus might fail on certain names.
    946806         </li>
     
    953813         </li>
    954814         <li>When a "filename" parameter is included as a fallback (as per above), "filename" should occur first, due to parsing problems
    955             in some existing implementations. <span class="comment" id="fallbackbug">[<a href="#fallbackbug" class="smpl">fallbackbug</a>: Firefox is known to pick the wrong parameter; a bug fix is scheduled for Firefox 5. --jre]</span>  <span class="comment" id="NOTE-TO-RFC-EDITOR">[<a href="#NOTE-TO-RFC-EDITOR" class="smpl">NOTE-TO-RFC-EDITOR</a>: PLEASE REMOVE THIS AND THE PRECEDING COMMENT BEFORE PUBLICATION AS RFC. --jre]</span>
     815            in some existing implementations.
    956816         </li>
    957817         <li>Use UTF-8 as the encoding of the "filename*" parameter, when present, because at least one existing implementation only implements
     
    962822         of this document, &lt;<a href="http://purl.org/NET/http/content-disposition-tests">http://purl.org/NET/http/content-disposition-tests</a>&gt; provides an overview of current levels of support in various implementations.
    963823      </p>
    964       <h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    965       <p id="rfc.section.E.p.1">Note: the issues names in the change log entries for draft-reschke-rfc2183-in-http refer to &lt;<a href="http://greenbytes.de/tech/webdav/draft-reschke-rfc2183-in-http-issues.html">http://greenbytes.de/tech/webdav/draft-reschke-rfc2183-in-http-issues.html</a>&gt;.
    966       </p>
    967       <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;Since draft-reschke-rfc2183-in-http-00
    968       </h2>
    969       <p id="rfc.section.E.1.p.1">Adjust terminology ("header" -&gt; "header field"). Update rfc2231-in-http reference.</p>
    970       <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;Since draft-reschke-rfc2183-in-http-01
    971       </h2>
    972       <p id="rfc.section.E.2.p.1">Update rfc2231-in-http reference. Actually define the "filename" parameter. Add internationalization considerations. Add examples
    973          using the RFC 5987 encoding. Add overview over other approaches, plus a table reporting implementation status. Add and resolve
    974          issue "nodep2183". Add issues "asciivsiso", "deplboth", "quoted", and "registry".
    975       </p>
    976       <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a>&nbsp;Since draft-reschke-rfc2183-in-http-02
    977       </h2>
    978       <p id="rfc.section.E.3.p.1">Add and close issue "docfallback". Close issues "asciivsiso", "deplboth", "quoted", and "registry".</p>
    979       <h2 id="rfc.section.E.4"><a href="#rfc.section.E.4">E.4</a>&nbsp;Since draft-reschke-rfc2183-in-http-03
    980       </h2>
    981       <p id="rfc.section.E.4.p.1">Updated to be a Working Draft of the IETF HTTPbis Working Group.</p>
    982       <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;<a id="changes.since.00" href="#changes.since.00">Since draft-ietf-httpbis-content-disp-00</a></h2>
    983       <p id="rfc.section.E.5.p.1">Closed issues: </p>
    984       <ul>
    985          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/242">http://tools.ietf.org/wg/httpbis/trac/ticket/242</a>&gt;: "handling of unknown disposition types"
    986          </li>
    987       </ul>
    988       <p id="rfc.section.E.5.p.2">Slightly updated the notes about the proposed fallback behavior.</p>
    989       <h2 id="rfc.section.E.6"><a href="#rfc.section.E.6">E.6</a>&nbsp;<a id="changes.since.01" href="#changes.since.01">Since draft-ietf-httpbis-content-disp-01</a></h2>
    990       <p id="rfc.section.E.6.p.1">Various editorial improvements.</p>
    991       <h2 id="rfc.section.E.7"><a href="#rfc.section.E.7">E.7</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-content-disp-02</a></h2>
    992       <p id="rfc.section.E.7.p.1">Closed issues: </p>
    993       <ul>
    994          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/244">http://tools.ietf.org/wg/httpbis/trac/ticket/244</a>&gt;: "state that repeating parameters are invalid"
    995          </li>
    996          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/245">http://tools.ietf.org/wg/httpbis/trac/ticket/245</a>&gt;: "warn about %xx in filenames being misinterpreted"
    997          </li>
    998          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/246">http://tools.ietf.org/wg/httpbis/trac/ticket/246</a>&gt;: "mention control chars when talking about postprecessing the filename parameter"
    999          </li>
    1000       </ul>
    1001       <p id="rfc.section.E.7.p.2">Update <a href="#alternatives.implementations" title="Implementations (to be removed by RFC Editor before publication)">Appendix&nbsp;C.4</a>; Opera 10.63 RC implements the recommended fallback behavior.
    1002       </p>
    1003       <h2 id="rfc.section.E.8"><a href="#rfc.section.E.8">E.8</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-content-disp-03</a></h2>
    1004       <p id="rfc.section.E.8.p.1">Closed issues: </p>
    1005       <ul>
    1006          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/252">http://tools.ietf.org/wg/httpbis/trac/ticket/252</a>&gt;: "'modification-date' *is* implemented in Konq 4.5"
    1007          </li>
    1008          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/253">http://tools.ietf.org/wg/httpbis/trac/ticket/253</a>&gt;: "clarify what LWS means for the Content-Disp grammar"
    1009          </li>
    1010          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/258">http://tools.ietf.org/wg/httpbis/trac/ticket/258</a>&gt;: "Avoid passive voice in message requirements"
    1011          </li>
    1012          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/263">http://tools.ietf.org/wg/httpbis/trac/ticket/263</a>&gt;: "text about historical percent-decoding unclear"
    1013          </li>
    1014          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/264">http://tools.ietf.org/wg/httpbis/trac/ticket/264</a>&gt;: "add explanation of language tagging"
    1015          </li>
    1016          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/265">http://tools.ietf.org/wg/httpbis/trac/ticket/265</a>&gt;: "Clarify that C-D spec does not apply to multipart upload"
    1017          </li>
    1018       </ul>
    1019       <h2 id="rfc.section.E.9"><a href="#rfc.section.E.9">E.9</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-content-disp-04</a></h2>
    1020       <p id="rfc.section.E.9.p.1">Updated implementation information (Chrome 9 implements RFC 5987, IE 9 RC implements it for UTF-8 only).</p>
    1021       <p id="rfc.section.E.9.p.2">Clarify who requirements are on, add a section discussing conformance and handling of invalid field values in general.</p>
    1022       <p id="rfc.section.E.9.p.3">Closed issues: </p>
    1023       <ul>
    1024          <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/243">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/243</a>&gt;: "avoid stating ISO-8859-1 default for header param" (the default is still mentioned, but it was clarified what it applies
    1025             to).
    1026          </li>
    1027          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/272">http://tools.ietf.org/wg/httpbis/trac/ticket/272</a>&gt;: "Path Separator Characters"
    1028          </li>
    1029       </ul>
    1030       <h2 id="rfc.section.E.10"><a href="#rfc.section.E.10">E.10</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-content-disp-05</a></h2>
    1031       <p id="rfc.section.E.10.p.1">Editorial changes: Fixed two typos where the new Conformance section said "Content-Location" instead of "Content-Disposition".
    1032          Cleaned up terminology ("user agent", "recipient", "sender", "message body", ...). Stated what the escape character for quoted-string
    1033          is. Explained a use case for "inline" disposition type. Updated implementation notes with respect to the fallback behavior.
    1034       </p>
    1035       <p id="rfc.section.E.10.p.2">Added appendix "Advice on Generating Content-Disposition Header Fields".</p>
    1036       <h2 id="rfc.section.E.11"><a href="#rfc.section.E.11">E.11</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-content-disp-06</a></h2>
    1037       <p id="rfc.section.E.11.p.1">Closed issues: </p>
    1038       <ul>
    1039          <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/278">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/278</a>&gt;: "conformance language"
    1040          </li>
    1041       </ul>
    1042       <h2 id="rfc.section.E.12"><a href="#rfc.section.E.12">E.12</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-content-disp-07</a></h2>
    1043       <p id="rfc.section.E.12.p.1">Rephrase the requirement about well-known file system locations, and also clarify that by "last path segment" we mean the
    1044          actual filename. Added a forward reference from "invalid" to the section that defines a valid header field.
    1045       </p>
    1046       <h2 id="rfc.section.E.13"><a href="#rfc.section.E.13">E.13</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-content-disp-08</a></h2>
    1047       <p id="rfc.section.E.13.p.1">Update: Internet Explorer 9 is released. Various editorial improvements. Add US-ASCII reference. Strengthen file extension
    1048          handling requirement to MUST for those recipients that actually use file extensions to map media types.
    1049       </p>
    1050       <h2 id="rfc.section.E.14"><a href="#rfc.section.E.14">E.14</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-content-disp-09</a></h2>
    1051       <p id="rfc.section.E.14.p.1">Editorial changes made during RFC-Editor AUTH48 phase.</p>
    1052824      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    1053825      <p class="noprint"><a href="#rfc.index.C">C</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.U">U</a>
  • draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml

    r1293 r1294  
    2424  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
    2525  <!ENTITY mdash "&#8212;">
     26  <!ENTITY nbsp  "&#160;">
     27  <!ENTITY nbhy  "&#8209;">
    2628]>
    2729
    2830<rfc xmlns:x="http://purl.org/net/xml2rfc/ext" xmlns:ed="http://greenbytes.de/2002/rfcedit" ipr="trust200902" docName="draft-ietf-httpbis-content-disp-latest" category="std" x:maturity-level="proposed" xml:lang="en" updates="2616">
    2931        <front>
    30   <title abbrev="Content-Disposition in HTTP">Use of the Content-Disposition&#160;Header&#160;Field
    31   in the Hypertext&#160;Transfer&#160;Protocol&#160;(HTTP)</title>
     32  <title abbrev="Content-Disposition in HTTP">Use of the Content-Disposition&nbsp;Header&nbsp;Field
     33  in the Hypertext&nbsp;Transfer&nbsp;Protocol&nbsp;(HTTP)</title>
    3234  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke">
    3335    <organization abbrev="greenbytes">greenbytes GmbH</organization>
     
    5557    </t>
    5658  </abstract>
    57  
     59<!-- 
    5860  <note title="Editorial Note (To be removed by RFC Editor before publication)">
    5961    <t>
     
    7375    </t>
    7476  </note>
     77-->
    7578  </front>
    76 
    7779  <middle>
    7880
     
    333335</artwork>
    334336<postamble>
    335   Note: this uses the quoted-string form so that the space character
     337  Note: This uses the quoted-string form so that the space character
    336338  can be included.
    337339</postamble>
     
    361363</artwork>
    362364<postamble>
    363   Note: those user agents that do not support the RFC 5987 encoding ignore
     365  Note: Those user agents that do not support the RFC 5987 encoding ignore
    364366  "filename*" when it occurs after "filename".
    365367</postamble>
     
    516518  <reference anchor="ISO-8859-1">
    517519    <front>
    518       <title>Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1</title>
     520      <title>Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No.&nbsp;1</title>
    519521      <author>
    520522        <organization>International Organization for Standardization</organization>
     
    736738<t>
    737739  For completeness, the sections below describe the various approaches that
    738   have been tried, and explain how they are inferior to the RFC&#160;5987
     740  have been tried, and explain how they are inferior to the RFC&nbsp;5987
    739741  encoding used in this specification.
    740742</t>
     
    791793</section>
    792794
    793 <section title="Implementations (to be removed by RFC Editor before publication)" anchor="alternatives.implementations">
     795<!--<section title="Implementations (to be removed by RFC Editor before publication)" anchor="alternatives.implementations">
    794796<t>
    795797  Unfortunately, as of March 2011, neither the encoding defined in RFCs 2231
     
    846848  <c>yes</c>
    847849</texttable>
    848 
    849850<t>
    850851  (*) Does not implement the fallback behavior to "filename" described in
     
    854855  (**) Starting with Internet Explorer 9, but only implements UTF-8.
    855856</t>
    856 
    857 </section>
    858 
     857</section>
     858-->
    859859</section>
    860860
     
    879879    and "\" can be considered an illegal path character.</t>
    880880    <t>Avoid using non-ASCII characters in the filename parameter. Although
    881     most existing implementations will decode them as ISO-8859-1, some
     881    most existing implementations will decode them as ISO&nbhy;8859&nbhy;1, some
    882882    will apply heuristics to detect UTF-8, and thus might fail on certain names.</t>
    883883    <t>Include a "filename*" parameter where the desired filename cannot be
     
    895895    <t>When a "filename" parameter is included as a fallback (as per above),
    896896    "filename" should occur first, due to parsing problems in some existing
    897     implementations.
     897    implementations.<!--
    898898    <cref anchor="fallbackbug" source="jre">
    899899    Firefox is known to pick the wrong parameter; a bug fix is scheduled for
    900900    Firefox 5.</cref>
    901901    <cref anchor="NOTE-TO-RFC-EDITOR" source="jre">
    902     PLEASE REMOVE THIS AND THE PRECEDING COMMENT BEFORE PUBLICATION AS RFC.</cref>
     902    PLEASE REMOVE THIS AND THE PRECEDING COMMENT BEFORE PUBLICATION AS RFC.</cref>-->
    903903    </t>
    904904    <t>Use UTF-8 as the encoding of the "filename*" parameter, when present,
     
    914914</section>
    915915
    916 <section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log">
     916<!--<section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log">
    917917<t>
    918918  Note: the issues names in the change log entries for draft-reschke-rfc2183-in-http
     
    11091109</section>
    11101110
    1111 
     1111-->
    11121112  </back>
    11131113
Note: See TracChangeset for help on using the changeset viewer.