Changeset 1075
- Timestamp:
- 04/11/10 08:16:27 (12 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
r1074 r1075 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2010-11-0 3">406 <meta name="dct.issued" scheme="ISO8601" content="2010-11-04"> 407 407 <meta name="dct.abstract" content="HTTP/1.1 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects."> 408 408 <meta name="description" content="HTTP/1.1 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects."> … … 422 422 <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 423 423 </td> 424 <td class="right">November 3, 2010</td>424 <td class="right">November 4, 2010</td> 425 425 </tr> 426 426 <tr> … … 429 429 </tr> 430 430 <tr> 431 <td class="left">Expires: May 7, 2011</td>431 <td class="left">Expires: May 8, 2011</td> 432 432 <td class="right"></td> 433 433 </tr> … … 458 458 in progress”. 459 459 </p> 460 <p>This Internet-Draft will expire on May 7, 2011.</p>460 <p>This Internet-Draft will expire on May 8, 2011.</p> 461 461 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 462 462 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 741 741 </tr> 742 742 <tr> 743 <td class="reference"><b id="RFC3629">[RFC3629]</b></td>744 <td class="top"><a href="mailto:fyergeau@alis.com" title="Alis Technologies">Yergeau, F.</a>, “<a href="http://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>”, STD 63, RFC 3629, November 2003.745 </td>746 </tr>747 <tr>748 743 <td class="reference"><b id="RFC3864">[RFC3864]</b></td> 749 744 <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP 90, RFC 3864, September 2004. … … 804 799 </p> 805 800 <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a> <a id="alternatives.percent" href="#alternatives.percent">Percent Encoding</a></h2> 806 <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. 801 <p id="rfc.section.C.2.p.1">Some user agents accept percent encoded (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>) sequences of characters. The character encoding being used for decoding depends on various factors, including the encoding 802 of the referring page, the user agent's locale, it's configuration, and also the actual value of the parameter. 807 803 </p> 808 804 <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 809 to the user. 810 </p> 811 <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 812 to use in multi-lingual environments. 805 to the user. For those user agents that do implement this it is difficult to predict what character encoding they actually 806 expect. 813 807 </p> 814 808 <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a> <a id="alternatives.sniff" href="#alternatives.sniff">Encoding Sniffing</a></h2> … … 929 923 </li> 930 924 <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" 925 </li> 926 <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" 931 927 </li> 932 928 <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" … … 978 974 </ul> 979 975 </li> 980 <li><em>RFC3629</em> <a href="#RFC3629"><b>9.2</b></a>, <a href="#rfc.xref.RFC3629.1">C.2</a></li>981 976 <li><em>RFC3864</em> <a href="#rfc.xref.RFC3864.1">7.2</a>, <a href="#RFC3864"><b>9.2</b></a></li> 982 977 <li><em>RFC3986</em> <a href="#RFC3986"><b>9.2</b></a>, <a href="#rfc.xref.RFC3986.1">C.2</a><ul> -
draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml
r1074 r1075 544 544 <seriesInfo name="RFC" value="2231"/> 545 545 </reference> 546 546 <!-- 547 547 <reference anchor="RFC3629"> 548 548 <front> … … 556 556 <seriesInfo name="STD" value="63"/> 557 557 <seriesInfo name="RFC" value="3629"/> 558 </reference> 558 </reference>--> 559 559 560 560 <reference anchor="RFC3864"> … … 693 693 <t> 694 694 Some user agents accept percent encoded (<xref target="RFC3986" x:fmt="," x:sec="2.1"/>) 695 sequences of characters encoded using the UTF-8 (<xref target="RFC3629"/>) character encoding.696 </t> 697 <t> 698 In practice, this is hard to use because those user agents699 that do not support it will display the escaped character sequence to the user. 700 < /t>701 <t> 702 Furthermore, the first user agent to implement this did choose the encoding703 based on local settings; thus making it very hard to use in multi-lingual704 en vironments.695 sequences of characters. The character encoding being used for decoding 696 depends on various factors, including the encoding of the referring page, 697 the user agent's locale, it's configuration, and also the actual value of 698 the parameter. 699 </t> 700 <t> 701 In practice, this is hard to use because those user agents that do not 702 support it will display the escaped character sequence to the user. For those 703 user agents that do implement this it is difficult to predict what character 704 encoding they actually expect. 705 705 </t> 706 706 </section> … … 886 886 </t> 887 887 <t> 888 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/263"/>: 889 "text about historical percent-decoding unclear" 890 </t> 891 <t> 888 892 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/264"/>: 889 893 "add explanation of language tagging"
Note: See TracChangeset
for help on using the changeset viewer.