![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 309
- Timestamp:
- 11/08/08 06:10:18 (15 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
-
p1-messaging.html (modified) (8 diffs)
-
p1-messaging.xml (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r308 r309 476 476 <tr> 477 477 <td class="header left"></td> 478 <td class="header right">August 1 0, 2008</td>478 <td class="header right">August 11, 2008</td> 479 479 </tr> 480 480 </table> … … 1010 1010 will be replaced with a single SP before interpretation of the TEXT value. 1011 1011 </p> 1012 <div id="rule.HEX ">1012 <div id="rule.HEXDIG"> 1013 1013 <p id="rfc.section.2.2.p.10"> Hexadecimal numeric characters are used in several protocol elements.</p> 1014 1014 </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" 1016 1016 | "a" | "b" | "c" | "d" | "e" | "f" | <a href="#core.rules" class="smpl">DIGIT</a> 1017 1017 </pre><div id="rule.token.separators"> … … 1139 1139 <li>An empty path-absolute is equivalent to an path-absolute of "/".</li> 1140 1140 </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. 1142 1142 </p> 1143 1143 <p id="rfc.section.3.2.3.p.3">For example, the following three URIs are equivalent:</p> … … 1259 1259 <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> 1260 1260 <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> 1262 1262 <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> 1263 1263 … … 1499 1499 URI, it <em class="bcp14">MUST</em> be given as "/" (the server root). 1500 1500 </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 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 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. 1502 1502 </p> 1503 1503 <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 … … 2739 2739 <ul> 2740 2740 <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> 2741 2742 </ul> 2742 2743 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> … … 2830 2831 <li class="indline1"><tt>general-header</tt> <a class="iref" href="#rfc.iref.g.71"><b>4.5</b></a></li> 2831 2832 <li class="indline1"><tt>generic-message</tt> <a class="iref" href="#rfc.iref.g.64"><b>4.1</b></a></li> 2832 <li class="indline1"><tt>HEX </tt> <a class="iref" href="#rfc.iref.g.15"><b>2.2</b></a></li>2833 <li class="indline1"><tt>HEXDIG</tt> <a class="iref" href="#rfc.iref.g.15"><b>2.2</b></a></li> 2833 2834 <li class="indline1"><tt>Host</tt> <a class="iref" href="#rfc.iref.g.86"><b>8.4</b></a></li> 2834 2835 <li class="indline1"><tt>HTAB</tt> <a class="iref" href="#rfc.iref.g.10"><b>2.2</b></a></li> … … 3001 3002 <li class="indline1"><em>RFC2324</em> <a class="iref" href="#rfc.xref.RFC2324.1">1.1</a>, <a class="iref" href="#RFC2324"><b>12.2</b></a></li> 3002 3003 <li class="indline1"><em>RFC2396</em> <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> <a class="iref" href="#rfc.xref.RFC2396.11">5.1.2</a></li> 3005 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.RFC2396.10">3.2.3</a></li> 3003 3006 <li class="indline1"><em>Section 3.2.2</em> <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> 3004 3007 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.RFC2396.3">3.2.1</a></li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r308 r309 884 884 replaced with a single SP before interpretation of the TEXT value. 885 885 </t> 886 <t anchor="rule.HEX ">887 <x:anchor-alias value="HEX "/>886 <t anchor="rule.HEXDIG"> 887 <x:anchor-alias value="HEXDIG"/> 888 888 Hexadecimal numeric characters are used in several protocol elements. 889 889 </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" 892 892 | "a" | "b" | "c" | "d" | "e" | "f" | <x:ref>DIGIT</x:ref> 893 893 </artwork></figure> … … 1156 1156 <t> 1157 1157 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. 1159 1160 </t> 1160 1161 <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> 1374 1375 <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> 1376 1377 <x:ref>last-chunk</x:ref> = 1*("0") [ <x:ref>chunk-extension</x:ref> ] <x:ref>CRLF</x:ref> 1377 1378 … … 1848 1849 <t> 1849 1850 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 1852 1855 properly interpret the request. Servers &SHOULD; respond to invalid 1853 1856 Request-URIs with an appropriate status code. … … 4606 4609 Replace string literals when the string really is case-sensitive (HTTP-Date). 4607 4610 </t> 4611 <t> 4612 Replace HEX by HEXDIG for future consistence with RFC 5234's core rules. 4613 </t> 4608 4614 </list> 4609 4615 </t>
Note: See TracChangeset
for help on using the changeset viewer.
