Changeset 1075

Timestamp:

04/11/10 08:16:27 (10 years ago)

Author:

julian.reschke@…

Message:

rephrase description of percent-encoding (see #263)

Location:

draft-ietf-httpbis-content-disp/latest

Files:

• draft-ietf-httpbis-content-disp.html (modified) (8 diffs)
• draft-ietf-httpbis-content-disp.xml (modified) (4 diffs)

draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html

@@ -404 +404 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2010-11-03">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-11-04">
       <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.">
       <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)
                </td>
-               <td class="right">November 3, 2010</td>
+               <td class="right">November 4, 2010</td>
             </tr>
             <tr>
@@ -429 +429 @@
             </tr>
             <tr>
-               <td class="left">Expires: May 7, 2011</td>
+               <td class="left">Expires: May 8, 2011</td>
                <td class="right"></td>
             </tr>
@@ -458 +458 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on May 7, 2011.</p>
+      <p>This Internet-Draft will expire on May 8, 2011.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -741 +741 @@
          </tr>
          <tr>
-            <td class="reference"><b id="RFC3629">[RFC3629]</b></td>
-            <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&nbsp;63, RFC&nbsp;3629, November&nbsp;2003.
-            </td>
-         </tr>
-         <tr>
             <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
             <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.
@@ -804 +799 @@
       </p>
       <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>
-      <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.
+      <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
+         of the referring page, the user agent's locale, it's configuration, and also the actual value of the parameter.
       </p>
       <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
-         to the user.
-      </p>
-      <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
-         to use in multi-lingual environments.
+         to the user. For those user agents that do implement this it is difficult to predict what character encoding they actually
+         expect.
       </p>
       <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>
@@ -929 +923 @@
          </li>
          <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"
+         </li>
+         <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"
          </li>
          <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"
@@ -978 +974 @@
                      </ul>
                   </li>
-                  <li><em>RFC3629</em>&nbsp;&nbsp;<a href="#RFC3629"><b>9.2</b></a>, <a href="#rfc.xref.RFC3629.1">C.2</a></li>
                   <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">7.2</a>, <a href="#RFC3864"><b>9.2</b></a></li>
                   <li><em>RFC3986</em>&nbsp;&nbsp;<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

@@ -544 +544 @@
     <seriesInfo name="RFC" value="2231"/>
   </reference>
-
+<!--
   <reference anchor="RFC3629">
     <front>
@@ -556 +556 @@
     <seriesInfo name="STD" value="63"/>
     <seriesInfo name="RFC" value="3629"/>
-  </reference>
+  </reference>-->
 
   <reference anchor="RFC3864">
@@ -693 +693 @@
 <t>
   Some user agents accept percent encoded (<xref target="RFC3986" x:fmt="," x:sec="2.1"/>)
-  sequences of characters encoded using the UTF-8 (<xref target="RFC3629"/>) character encoding.
-</t>
-<t>
-  In practice, this is hard to use because those user agents
-  that do not support it will display the escaped character sequence to the user.
-</t>
-<t>
-  Furthermore, the first user agent to implement this did choose the encoding
-  based on local settings; thus making it very hard to use in multi-lingual
-  environments.
+  sequences of characters. The character encoding being used for decoding
+  depends on various factors, including the encoding of the referring page,
+  the user agent's locale, it's configuration, and also the actual value of
+  the parameter.
+</t>
+<t>
+  In practice, this is hard to use because those user agents that do not
+  support it will display the escaped character sequence to the user. For those
+  user agents that do implement this it is difficult to predict what character
+  encoding they actually expect.
 </t>
 </section>
@@ -886 +886 @@
     </t>
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/263"/>:
+      "text about historical percent-decoding unclear"
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/264"/>:
       "add explanation of language tagging"