Changeset 1294
- Timestamp:
- 27/05/11 09:29:57 (11 years ago)
- 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 138 138 margin-left: 2em; 139 139 } 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 186 140 table.header { 187 141 border-spacing: 1px; … … 407 361 <link rel="Appendix" title="C Alternative Approaches to Internationalization" href="#rfc.section.C"> 408 362 <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">410 363 <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/"> 411 364 <link rel="schema.dct" href="http://purl.org/dc/terms/"> … … 448 401 aspects. 449 402 </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 currently452 revised by the IETF HTTPbis working group. See also <<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/123">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/123</a>>.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 issues455 list is at <<a href="http://trac.tools.ietf.org/wg/httpbis/trac/query?component=content-disp">http://trac.tools.ietf.org/wg/httpbis/trac/query?component=content-disp</a>> and related documents (including fancy diffs) can be found at <<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>>.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 E.14</a>.458 </p>459 403 <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1> 460 404 <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p> … … 509 453 <li>C.2 <a href="#alternatives.percent">Percent Encoding</a></li> 510 454 <li>C.3 <a href="#alternatives.sniff">Encoding Sniffing</a></li> 511 <li>C.4 <a href="#alternatives.implementations">Implementations (to be removed by RFC Editor before publication)</a></li>512 455 </ul> 513 456 </li> 514 457 <li>D. <a href="#advice.generating">Advice on Generating Content-Disposition Header Fields</a></li> 515 <li>E. <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>516 <li>E.1 <a href="#rfc.section.E.1">Since draft-reschke-rfc2183-in-http-00</a></li>517 <li>E.2 <a href="#rfc.section.E.2">Since draft-reschke-rfc2183-in-http-01</a></li>518 <li>E.3 <a href="#rfc.section.E.3">Since draft-reschke-rfc2183-in-http-02</a></li>519 <li>E.4 <a href="#rfc.section.E.4">Since draft-reschke-rfc2183-in-http-03</a></li>520 <li>E.5 <a href="#changes.since.00">Since draft-ietf-httpbis-content-disp-00</a></li>521 <li>E.6 <a href="#changes.since.01">Since draft-ietf-httpbis-content-disp-01</a></li>522 <li>E.7 <a href="#changes.since.02">Since draft-ietf-httpbis-content-disp-02</a></li>523 <li>E.8 <a href="#changes.since.03">Since draft-ietf-httpbis-content-disp-03</a></li>524 <li>E.9 <a href="#changes.since.04">Since draft-ietf-httpbis-content-disp-04</a></li>525 <li>E.10 <a href="#changes.since.05">Since draft-ietf-httpbis-content-disp-05</a></li>526 <li>E.11 <a href="#changes.since.06">Since draft-ietf-httpbis-content-disp-06</a></li>527 <li>E.12 <a href="#changes.since.07">Since draft-ietf-httpbis-content-disp-07</a></li>528 <li>E.13 <a href="#changes.since.08">Since draft-ietf-httpbis-content-disp-08</a></li>529 <li>E.14 <a href="#changes.since.09">Since draft-ietf-httpbis-content-disp-09</a></li>530 </ul>531 </li>532 458 <li><a href="#rfc.index">Index</a></li> 533 459 </ul> … … 624 550 being displayed). 625 551 </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. 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. 1">[ISO-8859-1]</cite></a>). 627 553 </p> 628 554 <p id="rfc.section.4.3.p.4">Many user agent implementations predating this specification do not understand the "filename*" parameter. Therefore, when … … 678 604 for a subsequent save operation: 679 605 </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> 681 607 <div id="rfc.figure.u.6"></div> 682 608 <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; … … 690 616 filename="EURO rates"; 691 617 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> 693 619 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="i18n" href="#i18n">Internationalization Considerations</a></h1> 694 620 <p id="rfc.section.6.p.1">The "filename*" parameter (<a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section 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 … … 738 664 <tr> 739 665 <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. 666 <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 8859-1:1998, 1998.</td> 741 667 </tr> 742 668 <tr> … … 824 750 </p> 825 751 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <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. 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. 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. 827 753 </p> 828 754 <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 … … 859 785 </p> 860 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> 861 <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a> <a id="alternatives.implementations" href="#alternatives.implementations">Implementations (to be removed by RFC Editor before publication)</a></h2>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 discussed863 above was implemented interoperably. Thus, this specification recommends the approach defined in RFC 5987, which at least864 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 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>927 787 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="advice.generating" href="#advice.generating">Advice on Generating Content-Disposition Header Fields</a></h1> 928 788 <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 … … 942 802 user agents, and "\" can be considered an illegal path character. 943 803 </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, 945 805 some will apply heuristics to detect UTF-8, and thus might fail on certain names. 946 806 </li> … … 953 813 </li> 954 814 <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. 956 816 </li> 957 817 <li>Use UTF-8 as the encoding of the "filename*" parameter, when present, because at least one existing implementation only implements … … 962 822 of this document, <<a href="http://purl.org/NET/http/content-disposition-tests">http://purl.org/NET/http/content-disposition-tests</a>> provides an overview of current levels of support in various implementations. 963 823 </p> 964 <h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a> <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 <<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>>.966 </p>967 <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a> Since draft-reschke-rfc2183-in-http-00968 </h2>969 <p id="rfc.section.E.1.p.1">Adjust terminology ("header" -> "header field"). Update rfc2231-in-http reference.</p>970 <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a> Since draft-reschke-rfc2183-in-http-01971 </h2>972 <p id="rfc.section.E.2.p.1">Update rfc2231-in-http reference. Actually define the "filename" parameter. Add internationalization considerations. Add examples973 using the RFC 5987 encoding. Add overview over other approaches, plus a table reporting implementation status. Add and resolve974 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> Since draft-reschke-rfc2183-in-http-02977 </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> Since draft-reschke-rfc2183-in-http-03980 </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> <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> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/242">http://tools.ietf.org/wg/httpbis/trac/ticket/242</a>>: "handling of unknown disposition types"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> <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> <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> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/244">http://tools.ietf.org/wg/httpbis/trac/ticket/244</a>>: "state that repeating parameters are invalid"995 </li>996 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/245">http://tools.ietf.org/wg/httpbis/trac/ticket/245</a>>: "warn about %xx in filenames being misinterpreted"997 </li>998 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/246">http://tools.ietf.org/wg/httpbis/trac/ticket/246</a>>: "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 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> <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> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/252">http://tools.ietf.org/wg/httpbis/trac/ticket/252</a>>: "'modification-date' *is* implemented in Konq 4.5"1007 </li>1008 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/253">http://tools.ietf.org/wg/httpbis/trac/ticket/253</a>>: "clarify what LWS means for the Content-Disp grammar"1009 </li>1010 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/258">http://tools.ietf.org/wg/httpbis/trac/ticket/258</a>>: "Avoid passive voice in message requirements"1011 </li>1012 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/263">http://tools.ietf.org/wg/httpbis/trac/ticket/263</a>>: "text about historical percent-decoding unclear"1013 </li>1014 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/264">http://tools.ietf.org/wg/httpbis/trac/ticket/264</a>>: "add explanation of language tagging"1015 </li>1016 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/265">http://tools.ietf.org/wg/httpbis/trac/ticket/265</a>>: "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> <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> <<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/243">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/243</a>>: "avoid stating ISO-8859-1 default for header param" (the default is still mentioned, but it was clarified what it applies1025 to).1026 </li>1027 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/272">http://tools.ietf.org/wg/httpbis/trac/ticket/272</a>>: "Path Separator Characters"1028 </li>1029 </ul>1030 <h2 id="rfc.section.E.10"><a href="#rfc.section.E.10">E.10</a> <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-string1033 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> <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> <<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/278">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/278</a>>: "conformance language"1040 </li>1041 </ul>1042 <h2 id="rfc.section.E.12"><a href="#rfc.section.E.12">E.12</a> <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 the1044 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> <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 extension1048 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> <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>1052 824 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1053 825 <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 24 24 <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>"> 25 25 <!ENTITY mdash "—"> 26 <!ENTITY nbsp " "> 27 <!ENTITY nbhy "‑"> 26 28 ]> 27 29 28 30 <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"> 29 31 <front> 30 <title abbrev="Content-Disposition in HTTP">Use of the Content-Disposition& #160;Header Field31 in the Hypertext& #160;Transfer Protocol (HTTP)</title>32 <title abbrev="Content-Disposition in HTTP">Use of the Content-Disposition Header Field 33 in the Hypertext Transfer Protocol (HTTP)</title> 32 34 <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke"> 33 35 <organization abbrev="greenbytes">greenbytes GmbH</organization> … … 55 57 </t> 56 58 </abstract> 57 59 <!-- 58 60 <note title="Editorial Note (To be removed by RFC Editor before publication)"> 59 61 <t> … … 73 75 </t> 74 76 </note> 77 --> 75 78 </front> 76 77 79 <middle> 78 80 … … 333 335 </artwork> 334 336 <postamble> 335 Note: this uses the quoted-string form so that the space character337 Note: This uses the quoted-string form so that the space character 336 338 can be included. 337 339 </postamble> … … 361 363 </artwork> 362 364 <postamble> 363 Note: those user agents that do not support the RFC 5987 encoding ignore365 Note: Those user agents that do not support the RFC 5987 encoding ignore 364 366 "filename*" when it occurs after "filename". 365 367 </postamble> … … 516 518 <reference anchor="ISO-8859-1"> 517 519 <front> 518 <title>Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 520 <title>Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1</title> 519 521 <author> 520 522 <organization>International Organization for Standardization</organization> … … 736 738 <t> 737 739 For completeness, the sections below describe the various approaches that 738 have been tried, and explain how they are inferior to the RFC& #160;5987740 have been tried, and explain how they are inferior to the RFC 5987 739 741 encoding used in this specification. 740 742 </t> … … 791 793 </section> 792 794 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"> 794 796 <t> 795 797 Unfortunately, as of March 2011, neither the encoding defined in RFCs 2231 … … 846 848 <c>yes</c> 847 849 </texttable> 848 849 850 <t> 850 851 (*) Does not implement the fallback behavior to "filename" described in … … 854 855 (**) Starting with Internet Explorer 9, but only implements UTF-8. 855 856 </t> 856 857 </section> 858 857 </section> 858 --> 859 859 </section> 860 860 … … 879 879 and "\" can be considered an illegal path character.</t> 880 880 <t>Avoid using non-ASCII characters in the filename parameter. Although 881 most existing implementations will decode them as ISO -8859-1, some881 most existing implementations will decode them as ISO&nbhy;8859&nbhy;1, some 882 882 will apply heuristics to detect UTF-8, and thus might fail on certain names.</t> 883 883 <t>Include a "filename*" parameter where the desired filename cannot be … … 895 895 <t>When a "filename" parameter is included as a fallback (as per above), 896 896 "filename" should occur first, due to parsing problems in some existing 897 implementations. 897 implementations.<!-- 898 898 <cref anchor="fallbackbug" source="jre"> 899 899 Firefox is known to pick the wrong parameter; a bug fix is scheduled for 900 900 Firefox 5.</cref> 901 901 <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>--> 903 903 </t> 904 904 <t>Use UTF-8 as the encoding of the "filename*" parameter, when present, … … 914 914 </section> 915 915 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"> 917 917 <t> 918 918 Note: the issues names in the change log entries for draft-reschke-rfc2183-in-http … … 1109 1109 </section> 1110 1110 1111 1111 --> 1112 1112 </back> 1113 1113
Note: See TracChangeset
for help on using the changeset viewer.