Changeset 309


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)

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r308 r309  
    476476         <tr>
    477477            <td class="header left"></td>
    478             <td class="header right">August 10, 2008</td>
     478            <td class="header right">August 11, 2008</td>
    479479         </tr>
    480480      </table>
     
    10101010         will be replaced with a single SP before interpretation of the TEXT value.
    10111011      </p>
    1012       <div id="rule.HEX">
     1012      <div id="rule.HEXDIG">
    10131013         <p id="rfc.section.2.2.p.10">  Hexadecimal numeric characters are used in several protocol elements.</p>
    10141014      </div>
    1015       <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.15"></span>  <a href="#rule.HEX" class="smpl">HEX</a>            = "A" | "B" | "C" | "D" | "E" | "F"
     1015      <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.15"></span>  <a href="#rule.HEXDIG" class="smpl">HEXDIG</a>         = "A" | "B" | "C" | "D" | "E" | "F"
    10161016                 | "a" | "b" | "c" | "d" | "e" | "f" | <a href="#core.rules" class="smpl">DIGIT</a>
    10171017</pre><div id="rule.token.separators">
     
    11391139         <li>An empty path-absolute is equivalent to an path-absolute of "/".</li>
    11401140      </ul>
    1141       <p id="rfc.section.3.2.3.p.2">Characters other than those in the "reserved" set (see <a href="#RFC2396" id="rfc.xref.RFC2396.10"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>) are equivalent to their ""%" HEX HEX" encoding.
     1141      <p id="rfc.section.3.2.3.p.2">Characters other than those in the "reserved" set (see <a href="#RFC2396" id="rfc.xref.RFC2396.10"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-2.2">Section 2.2</a>) are equivalent to their ""%" <a href="#rule.HEXDIG" class="smpl">HEXDIG</a>  <a href="#rule.HEXDIG" class="smpl">HEXDIG</a>" encoding.
    11421142      </p>
    11431143      <p id="rfc.section.3.2.3.p.3">For example, the following three URIs are equivalent:</p>
     
    12591259  <a href="#chunked.transfer.encoding" class="smpl">chunk</a>          = <a href="#chunked.transfer.encoding" class="smpl">chunk-size</a> [ <a href="#chunked.transfer.encoding" class="smpl">chunk-extension</a> ] <a href="#rule.CRLF" class="smpl">CRLF</a>
    12601260                   <a href="#chunked.transfer.encoding" class="smpl">chunk-data</a> <a href="#rule.CRLF" class="smpl">CRLF</a>
    1261   <a href="#chunked.transfer.encoding" class="smpl">chunk-size</a>     = 1*<a href="#rule.HEX" class="smpl">HEX</a>
     1261  <a href="#chunked.transfer.encoding" class="smpl">chunk-size</a>     = 1*<a href="#rule.HEXDIG" class="smpl">HEXDIG</a>
    12621262  <a href="#chunked.transfer.encoding" class="smpl">last-chunk</a>     = 1*("0") [ <a href="#chunked.transfer.encoding" class="smpl">chunk-extension</a> ] <a href="#rule.CRLF" class="smpl">CRLF</a>
    12631263 
     
    14991499         URI, it <em class="bcp14">MUST</em> be given as "/" (the server root).
    15001500      </p>
    1501       <p id="rfc.section.5.1.2.p.12">The Request-URI is transmitted in the format specified in <a href="#general.syntax" title="General Syntax">Section&nbsp;3.2.1</a>. If the Request-URI is encoded using the "% HEX HEX" encoding <a href="#RFC2396" id="rfc.xref.RFC2396.11"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, the origin server <em class="bcp14">MUST</em> decode the Request-URI in order to properly interpret the request. Servers <em class="bcp14">SHOULD</em> respond to invalid Request-URIs with an appropriate status code.
     1501      <p id="rfc.section.5.1.2.p.12">The Request-URI is transmitted in the format specified in <a href="#general.syntax" title="General Syntax">Section&nbsp;3.2.1</a>. If the Request-URI is encoded using the "% <a href="#rule.HEXDIG" class="smpl">HEXDIG</a>  <a href="#rule.HEXDIG" class="smpl">HEXDIG</a>" encoding (<a href="#RFC2396" id="rfc.xref.RFC2396.11"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-2.4.1">Section 2.4.1</a>), the origin server <em class="bcp14">MUST</em> decode the Request-URI in order to properly interpret the request. Servers <em class="bcp14">SHOULD</em> respond to invalid Request-URIs with an appropriate status code.
    15021502      </p>
    15031503      <p id="rfc.section.5.1.2.p.13">A transparent proxy <em class="bcp14">MUST NOT</em> rewrite the "path-absolute" part of the received Request-URI when forwarding it to the next inbound server, except as noted
     
    27392739      <ul>
    27402740         <li>Replace string literals when the string really is case-sensitive (HTTP-Date).</li>
     2741         <li>Replace HEX by HEXDIG for future consistence with RFC 5234's core rules.</li>
    27412742      </ul>
    27422743      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
     
    28302831                        <li class="indline1"><tt>general-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.71"><b>4.5</b></a></li>
    28312832                        <li class="indline1"><tt>generic-message</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.64"><b>4.1</b></a></li>
    2832                         <li class="indline1"><tt>HEX</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>2.2</b></a></li>
     2833                        <li class="indline1"><tt>HEXDIG</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>2.2</b></a></li>
    28332834                        <li class="indline1"><tt>Host</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.86"><b>8.4</b></a></li>
    28342835                        <li class="indline1"><tt>HTAB</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.10"><b>2.2</b></a></li>
     
    30013002                  <li class="indline1"><em>RFC2324</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2324.1">1.1</a>, <a class="iref" href="#RFC2324"><b>12.2</b></a></li>
    30023003                  <li class="indline1"><em>RFC2396</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.1">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.2">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.3">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.4">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.5">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.6">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.7">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.8">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.9">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.10">3.2.3</a>, <a class="iref" href="#rfc.xref.RFC2396.11">5.1.2</a>, <a class="iref" href="#RFC2396"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.RFC2396.12">C.4</a><ul class="ind">
     3004                        <li class="indline1"><em>Section 2.4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.11">5.1.2</a></li>
     3005                        <li class="indline1"><em>Section 2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.10">3.2.3</a></li>
    30033006                        <li class="indline1"><em>Section 3.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.6">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.9">3.2.1</a></li>
    30043007                        <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.3">3.2.1</a></li>
  • 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.