Ignore:
Timestamp:
Aug 10, 2008, 11:10:18 PM (11 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:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r308 r309  
    884884   replaced with a single SP before interpretation of the TEXT value.
    885885</t>
    886 <t anchor="rule.HEX">
    887   <x:anchor-alias value="HEX"/>
     886<t anchor="rule.HEXDIG">
     887  <x:anchor-alias value="HEXDIG"/>
    888888   Hexadecimal numeric characters are used in several protocol elements.
    889889</t>
    890 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HEX"/>
    891   <x:ref>HEX</x:ref>            = "A" | "B" | "C" | "D" | "E" | "F"
     890<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HEXDIG"/>
     891  <x:ref>HEXDIG</x:ref>         = "A" | "B" | "C" | "D" | "E" | "F"
    892892                 | "a" | "b" | "c" | "d" | "e" | "f" | <x:ref>DIGIT</x:ref>
    893893</artwork></figure>
     
    11561156<t>
    11571157   Characters other than those in the "reserved" set (see
    1158    <xref target="RFC2396"/>) are equivalent to their ""%" HEX HEX" encoding.
     1158   <xref target="RFC2396" x:fmt="," x:sec="2.2"/>) are equivalent to their
     1159   ""%" <x:ref>HEXDIG</x:ref> <x:ref>HEXDIG</x:ref>" encoding.
    11591160</t>
    11601161<t>
     
    13731374  <x:ref>chunk</x:ref>          = <x:ref>chunk-size</x:ref> [ <x:ref>chunk-extension</x:ref> ] <x:ref>CRLF</x:ref>
    13741375                   <x:ref>chunk-data</x:ref> <x:ref>CRLF</x:ref>
    1375   <x:ref>chunk-size</x:ref>     = 1*<x:ref>HEX</x:ref>
     1376  <x:ref>chunk-size</x:ref>     = 1*<x:ref>HEXDIG</x:ref>
    13761377  <x:ref>last-chunk</x:ref>     = 1*("0") [ <x:ref>chunk-extension</x:ref> ] <x:ref>CRLF</x:ref>
    13771378 
     
    18481849<t>
    18491850   The Request-URI is transmitted in the format specified in
    1850    <xref target="general.syntax"/>. If the Request-URI is encoded using the "% HEX HEX" encoding
    1851    <xref target="RFC2396"/>, the origin server &MUST; decode the Request-URI in order to
     1851   <xref target="general.syntax"/>. If the Request-URI is encoded using the
     1852   "% <x:ref>HEXDIG</x:ref> <x:ref>HEXDIG</x:ref>" encoding
     1853   (<xref target="RFC2396" x:fmt="," x:sec="2.4.1"/>), the origin server
     1854   &MUST; decode the Request-URI in order to
    18521855   properly interpret the request. Servers &SHOULD; respond to invalid
    18531856   Request-URIs with an appropriate status code.
     
    46064609      Replace string literals when the string really is case-sensitive (HTTP-Date).
    46074610    </t>
     4611    <t>
     4612      Replace HEX by HEXDIG for future consistence with RFC 5234's core rules.
     4613    </t>
    46084614  </list>
    46094615</t>
Note: See TracChangeset for help on using the changeset viewer.