Changeset 309 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

11/08/08 06:10:18 (15 years ago)

Author:

julian.reschke@…

Message:

s/HEX/HEXDIG/, also add section targets for some RFC2396 references related to percent escaping (related to #36)

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (5 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -884 +884 @@
    replaced with a single SP before interpretation of the TEXT value.
 </t>
-<t anchor="rule.HEX">
-  <x:anchor-alias value="HEX"/>
+<t anchor="rule.HEXDIG">
+  <x:anchor-alias value="HEXDIG"/>
    Hexadecimal numeric characters are used in several protocol elements.
 </t>
-<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HEX"/>
-  <x:ref>HEX</x:ref>            = "A" | "B" | "C" | "D" | "E" | "F"
+<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HEXDIG"/>
+  <x:ref>HEXDIG</x:ref>         = "A" | "B" | "C" | "D" | "E" | "F"
                  | "a" | "b" | "c" | "d" | "e" | "f" | <x:ref>DIGIT</x:ref>
 </artwork></figure>
@@ -1156 +1156 @@
 <t>
    Characters other than those in the "reserved" set (see
-   <xref target="RFC2396"/>) are equivalent to their ""%" HEX HEX" encoding.
+   <xref target="RFC2396" x:fmt="," x:sec="2.2"/>) are equivalent to their
+   ""%" <x:ref>HEXDIG</x:ref> <x:ref>HEXDIG</x:ref>" encoding.
 </t>
 <t>
@@ -1373 +1374 @@
   <x:ref>chunk</x:ref>          = <x:ref>chunk-size</x:ref> [ <x:ref>chunk-extension</x:ref> ] <x:ref>CRLF</x:ref>
                    <x:ref>chunk-data</x:ref> <x:ref>CRLF</x:ref>
-  <x:ref>chunk-size</x:ref>     = 1*<x:ref>HEX</x:ref>
+  <x:ref>chunk-size</x:ref>     = 1*<x:ref>HEXDIG</x:ref>
   <x:ref>last-chunk</x:ref>     = 1*("0") [ <x:ref>chunk-extension</x:ref> ] <x:ref>CRLF</x:ref>
   
@@ -1848 +1849 @@
 <t>
    The Request-URI is transmitted in the format specified in 
-   <xref target="general.syntax"/>. If the Request-URI is encoded using the "% HEX HEX" encoding
-   <xref target="RFC2396"/>, the origin server &MUST; decode the Request-URI in order to
+   <xref target="general.syntax"/>. If the Request-URI is encoded using the
+   "% <x:ref>HEXDIG</x:ref> <x:ref>HEXDIG</x:ref>" encoding
+   (<xref target="RFC2396" x:fmt="," x:sec="2.4.1"/>), the origin server
+   &MUST; decode the Request-URI in order to
    properly interpret the request. Servers &SHOULD; respond to invalid
    Request-URIs with an appropriate status code.
@@ -4606 +4609 @@
       Replace string literals when the string really is case-sensitive (HTTP-Date).
     </t>
+    <t>
+      Replace HEX by HEXDIG for future consistence with RFC 5234's core rules. 
+    </t>
   </list>
 </t>