![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 628
- Timestamp:
- 27/07/09 14:26:18 (13 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 13 edited
-
p1-messaging.html (modified) (1 diff)
-
p2-semantics.html (modified) (11 diffs)
-
p2-semantics.xml (modified) (4 diffs)
-
p3-payload.html (modified) (10 diffs)
-
p3-payload.xml (modified) (2 diffs)
-
p4-conditional.html (modified) (4 diffs)
-
p4-conditional.xml (modified) (1 diff)
-
p5-range.html (modified) (6 diffs)
-
p5-range.xml (modified) (2 diffs)
-
p6-cache.html (modified) (9 diffs)
-
p6-cache.xml (modified) (4 diffs)
-
p7-auth.html (modified) (2 diffs)
-
p7-auth.xml (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r627 r628 471 471 <tr> 472 472 <td class="header left"></td> 473 <td class="header right">July 2 6, 2009</td>473 <td class="header right">July 27, 2009</td> 474 474 </tr> 475 475 </table> -
draft-ietf-httpbis/latest/p2-semantics.html
r614 r628 471 471 <tr> 472 472 <td class="header left"></td> 473 <td class="header right">July 2 1, 2009</td>473 <td class="header right">July 27, 2009</td> 474 474 </tr> 475 475 </table> … … 699 699 </pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a> <a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3> 700 700 <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p> 701 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2. 1</a>>702 <a href="#abnf.dependencies" class="smpl">fragment</a> = <fragment, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2. 1</a>>703 <a href="#abnf.dependencies" class="smpl">Host</a> = <Host, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2. 1</a>>704 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 3.2</a>>705 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2. 1</a>>706 <a href="#abnf.dependencies" class="smpl">product</a> = <product, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.4</a>>701 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.3</a>> 702 <a href="#abnf.dependencies" class="smpl">fragment</a> = <fragment, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.3</a>> 703 <a href="#abnf.dependencies" class="smpl">Host</a> = <Host, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.3</a>> 704 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a>> 705 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.3</a>> 706 <a href="#abnf.dependencies" class="smpl">product</a> = <product, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a>> 707 707 <a href="#abnf.dependencies" class="smpl">TE</a> = <TE, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a>> 708 708 </pre><div id="rfc.figure.u.3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Accept</a> = <Accept, defined in <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 5.1</a>> … … 881 881 fields are defined in <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. 882 882 </p> 883 <p id="rfc.section.6.p.2">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure883 <p id="rfc.section.6.p.2">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure 884 884 safe and proper transfer of the message. 885 885 </p> … … 1459 1459 <p id="rfc.section.8.5.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server 1460 1460 is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described 1461 in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 3.1</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain an entity describing why that version is not supported and what other protocols are supported by that server.1461 in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 2.2</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain an entity describing why that version is not supported and what other protocols are supported by that server. 1462 1462 </p> 1463 1463 <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> <a id="header.fields" href="#header.fields">Header Field Definitions</a></h1> … … 1611 1611 <h2 id="rfc.section.9.8"><a href="#rfc.section.9.8">9.8</a> <a id="header.server" href="#header.server">Server</a></h2> 1612 1612 <p id="rfc.section.9.8.p.1">The response-header field "Server" contains information about the software used by the origin server to handle the request. 1613 The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.4</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the server and any significant subproducts. The product tokens are listed in order of their significance1613 The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the server and any significant subproducts. The product tokens are listed in order of their significance 1614 1614 for identifying the application. 1615 1615 </p> … … 1632 1632 <p id="rfc.section.9.9.p.1">The request-header field "User-Agent" contains information about the user agent originating the request. This is for statistical 1633 1633 purposes, the tracing of protocol violations, and automated recognition of user agents for the sake of tailoring responses 1634 to avoid particular user agent limitations. User agents <em class="bcp14">SHOULD</em> include this field with requests. The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.4</a> of <a href="#Part1" id="rfc.xref.Part1.27"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the agent and any subproducts which form a significant part of the user agent. By convention, the1634 to avoid particular user agent limitations. User agents <em class="bcp14">SHOULD</em> include this field with requests. The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.27"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the agent and any subproducts which form a significant part of the user agent. By convention, the 1635 1635 product tokens are listed in order of their significance for identifying the application. 1636 1636 </p> … … 2275 2275 <a href="#header.from" class="smpl">From-v</a> = mailbox 2276 2276 2277 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 3.2>2278 <a href="#abnf.dependencies" class="smpl">Host</a> = <Host, defined in [Part1], Section 2. 1>2277 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 6.1> 2278 <a href="#abnf.dependencies" class="smpl">Host</a> = <Host, defined in [Part1], Section 2.3> 2279 2279 2280 2280 <a href="#abnf.dependencies" class="smpl">If-Match</a> = <If-Match, defined in [Part4], Section 6.2> … … 2335 2335 <WWW-Authenticate, defined in [Part7], Section 3.4> 2336 2336 2337 <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, defined in [Part1], Section 2. 1>2337 <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, defined in [Part1], Section 2.3> 2338 2338 2339 2339 <a href="#core.rules" class="smpl">comment</a> = <comment, defined in [Part1], Section 1.2.2> … … 2348 2348 <a href="#method" class="smpl">extension-method</a> = token 2349 2349 2350 <a href="#abnf.dependencies" class="smpl">fragment</a> = <fragment, defined in [Part1], Section 2. 1>2350 <a href="#abnf.dependencies" class="smpl">fragment</a> = <fragment, defined in [Part1], Section 2.3> 2351 2351 2352 2352 <a href="#header.from" class="smpl">mailbox</a> = <mailbox, defined in [RFC5322], Section 3.4> … … 2354 2354 <a href="#core.rules" class="smpl">obs-text</a> = <obs-text, defined in [Part1], Section 1.2.2> 2355 2355 2356 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in [Part1], Section 2. 1>2357 <a href="#abnf.dependencies" class="smpl">product</a> = <product, defined in [Part1], Section 3.4>2356 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in [Part1], Section 2.3> 2357 <a href="#abnf.dependencies" class="smpl">product</a> = <product, defined in [Part1], Section 6.3> 2358 2358 2359 2359 <a href="#core.rules" class="smpl">quoted-string</a> = <quoted-string, defined in [Part1], Section 1.2.2> … … 2676 2676 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.2</a></li> 2677 2677 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.8">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.1</a></li> 2678 <li class="indline1"><em>Section 2. 1</em> <a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.11">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.12">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">1.2.2</a></li>2679 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part1.23">8.5.6</a></li>2680 <li class="indline1"><em>Section 3. 2</em> <a class="iref" href="#rfc.xref.Part1.13">1.2.2</a></li>2681 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.Part1.15">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.25">9.8</a>, <a class="iref" href="#rfc.xref.Part1.27">9.9</a></li>2682 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.19">6</a></li>2678 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.Part1.23">8.5.6</a></li> 2679 <li class="indline1"><em>Section 2.3</em> <a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.11">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.12">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">1.2.2</a></li> 2680 <li class="indline1"><em>Section 3.3</em> <a class="iref" href="#rfc.xref.Part1.19">6</a></li> 2681 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part1.13">1.2.2</a></li> 2682 <li class="indline1"><em>Section 6.3</em> <a class="iref" href="#rfc.xref.Part1.15">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.25">9.8</a>, <a class="iref" href="#rfc.xref.Part1.27">9.9</a></li> 2683 2683 <li class="indline1"><em>Section 7.2.3</em> <a class="iref" href="#rfc.xref.Part1.22">8.1.1</a>, <a class="iref" href="#rfc.xref.Part1.24">9.2</a></li> 2684 2684 <li class="indline1"><em>Section 8.4</em> <a class="iref" href="#rfc.xref.Part1.17">3</a></li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r614 r628 3267 3267 <x:ref>From-v</x:ref> = mailbox 3268 3268 3269 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 3.2>3270 <x:ref>Host</x:ref> = <Host, defined in [Part1], Section 2. 1>3269 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 6.1> 3270 <x:ref>Host</x:ref> = <Host, defined in [Part1], Section 2.3> 3271 3271 3272 3272 <x:ref>If-Match</x:ref> = <If-Match, defined in [Part4], Section 6.2> … … 3327 3327 <WWW-Authenticate, defined in [Part7], Section 3.4> 3328 3328 3329 <x:ref>absolute-URI</x:ref> = <absolute-URI, defined in [Part1], Section 2. 1>3329 <x:ref>absolute-URI</x:ref> = <absolute-URI, defined in [Part1], Section 2.3> 3330 3330 3331 3331 <x:ref>comment</x:ref> = <comment, defined in [Part1], Section 1.2.2> … … 3340 3340 <x:ref>extension-method</x:ref> = token 3341 3341 3342 <x:ref>fragment</x:ref> = <fragment, defined in [Part1], Section 2. 1>3342 <x:ref>fragment</x:ref> = <fragment, defined in [Part1], Section 2.3> 3343 3343 3344 3344 <x:ref>mailbox</x:ref> = <mailbox, defined in [RFC5322], Section 3.4> … … 3346 3346 <x:ref>obs-text</x:ref> = <obs-text, defined in [Part1], Section 1.2.2> 3347 3347 3348 <x:ref>partial-URI</x:ref> = <partial-URI, defined in [Part1], Section 2. 1>3349 <x:ref>product</x:ref> = <product, defined in [Part1], Section 3.4>3348 <x:ref>partial-URI</x:ref> = <partial-URI, defined in [Part1], Section 2.3> 3349 <x:ref>product</x:ref> = <product, defined in [Part1], Section 6.3> 3350 3350 3351 3351 <x:ref>quoted-string</x:ref> = <quoted-string, defined in [Part1], Section 1.2.2> -
draft-ietf-httpbis/latest/p3-payload.html
r613 r628 478 478 <tr> 479 479 <td class="header left"></td> 480 <td class="header right">July 19, 2009</td>480 <td class="header right">July 27, 2009</td> 481 481 </tr> 482 482 </table> … … 655 655 </pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a> <a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3> 656 656 <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p> 657 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2. 1</a>>657 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.3</a>> 658 658 <a href="#abnf.dependencies" class="smpl">Content-Length</a> = <Content-Length, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 8.2</a>> 659 <a href="#abnf.dependencies" class="smpl">message-header</a> = <message-header, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</a>>660 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2. 1</a>>661 <a href="#abnf.dependencies" class="smpl">qvalue</a> = <qvalue, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#quality.values" title="Quality Values">Section 3.5</a>>659 <a href="#abnf.dependencies" class="smpl">message-header</a> = <message-header, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#message.headers" title="Message Headers">Section 3.2</a>> 660 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.3</a>> 661 <a href="#abnf.dependencies" class="smpl">qvalue</a> = <qvalue, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#quality.values" title="Quality Values">Section 6.4</a>> 662 662 </pre><div id="rfc.figure.u.3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Last-Modified</a> = <Last-Modified, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 6.6</a>> 663 663 </pre><div id="rfc.figure.u.4"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Content-Range</a> = <Content-Range, defined in <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a>> … … 854 854 <p id="rfc.section.3.2.p.1">The entity-body (if any) sent with an HTTP request or response is in a format and encoding defined by the entity-header fields.</p> 855 855 <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.13"></span> <a href="#entity.body" class="smpl">entity-body</a> = *<a href="#notation" class="smpl">OCTET</a> 856 </pre><p id="rfc.section.3.2.p.3">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure856 </pre><p id="rfc.section.3.2.p.3">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure 857 857 safe and proper transfer of the message. 858 858 </p> … … 872 872 </p> 873 873 <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a> <a id="entity.length" href="#entity.length">Entity Length</a></h3> 874 <p id="rfc.section.3.2.2.p.1">The entity-length of a message is the length of the message-body before any transfer-codings have been applied. <a href="p1-messaging.html#message.length" title="Message Length">Section 4.4</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> defines how the transfer-length of a message-body is determined.874 <p id="rfc.section.3.2.2.p.1">The entity-length of a message is the length of the message-body before any transfer-codings have been applied. <a href="p1-messaging.html#message.length" title="Message Length">Section 3.4</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> defines how the transfer-length of a message-body is determined. 875 875 </p> 876 876 <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1> … … 981 981 <p id="rfc.section.5.1.p.4">Each media-range <em class="bcp14">MAY</em> be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative quality factor. The first 982 982 "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user 983 agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1.983 agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 6.4</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1. 984 984 </p> 985 985 <div class="note"> … … 1105 1105 <ol> 1106 1106 <li>If the content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable, unless it 1107 is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable.")1107 is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 6.4</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable.") 1108 1108 </li> 1109 1109 <li>The special "*" symbol in an Accept-Encoding field matches any available content-coding not explicitly listed in the header … … 1648 1648 </p> 1649 1649 <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a> <a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h2> 1650 <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary.1650 <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary. 1651 1651 </p> 1652 1652 <h2 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a> <a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h2> … … 1766 1766 <a href="#core.rules" class="smpl">OWS</a> = <OWS, defined in [Part1], Section 1.2.2> 1767 1767 1768 <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, defined in [Part1], Section 2. 1>1768 <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, defined in [Part1], Section 2.3> 1769 1769 <a href="#header.accept" class="smpl">accept-ext</a> = OWS ";" OWS token [ "=" ( token / quoted-string ) ] 1770 1770 <a href="#header.accept" class="smpl">accept-params</a> = OWS ";" OWS "q=" qvalue *accept-ext … … 1798 1798 ";" OWS parameter ) 1799 1799 <a href="#media.types" class="smpl">media-type</a> = type "/" subtype *( OWS ";" OWS parameter ) 1800 <a href="#abnf.dependencies" class="smpl">message-header</a> = <message-header, defined in [Part1], Section 4.2>1800 <a href="#abnf.dependencies" class="smpl">message-header</a> = <message-header, defined in [Part1], Section 3.2> 1801 1801 1802 1802 <a href="#rule.parameter" class="smpl">parameter</a> = attribute "=" value 1803 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in [Part1], Section 2. 1>1803 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in [Part1], Section 2.3> 1804 1804 1805 1805 <a href="#core.rules" class="smpl">quoted-string</a> = <quoted-string, defined in [Part1], Section 1.2.2> 1806 <a href="#abnf.dependencies" class="smpl">qvalue</a> = <qvalue, defined in [Part1], Section 3.5>1806 <a href="#abnf.dependencies" class="smpl">qvalue</a> = <qvalue, defined in [Part1], Section 6.4> 1807 1807 1808 1808 <a href="#media.types" class="smpl">subtype</a> = token … … 2061 2061 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a></li> 2062 2062 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a></li> 2063 <li class="indline1"><em>Section 2. 1</em> <a class="iref" href="#rfc.xref.Part1.6">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.2</a></li>2064 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1. 16">A.3</a></li>2065 <li class="indline1"><em>Section 3. 5</em> <a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">5.1</a>, <a class="iref" href="#rfc.xref.Part1.15">5.3</a></li>2066 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part1.8">1.2.2</a></li>2067 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.12">3.2</a></li>2068 <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part1.13">3.2.2</a></li>2063 <li class="indline1"><em>Section 2.3</em> <a class="iref" href="#rfc.xref.Part1.6">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.2</a></li> 2064 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1.8">1.2.2</a></li> 2065 <li class="indline1"><em>Section 3.3</em> <a class="iref" href="#rfc.xref.Part1.12">3.2</a></li> 2066 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.Part1.13">3.2.2</a></li> 2067 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part1.16">A.3</a></li> 2068 <li class="indline1"><em>Section 6.4</em> <a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">5.1</a>, <a class="iref" href="#rfc.xref.Part1.15">5.3</a></li> 2069 2069 <li class="indline1"><em>Section 8.2</em> <a class="iref" href="#rfc.xref.Part1.7">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.11">3.1</a></li> 2070 2070 <li class="indline1"><em>Section 8.7</em> <a class="iref" href="#rfc.xref.Part1.17">A.6</a></li> -
draft-ietf-httpbis/latest/p3-payload.xml
r613 r628 2707 2707 <x:ref>OWS</x:ref> = <OWS, defined in [Part1], Section 1.2.2> 2708 2708 2709 <x:ref>absolute-URI</x:ref> = <absolute-URI, defined in [Part1], Section 2. 1>2709 <x:ref>absolute-URI</x:ref> = <absolute-URI, defined in [Part1], Section 2.3> 2710 2710 <x:ref>accept-ext</x:ref> = OWS ";" OWS token [ "=" ( token / quoted-string ) ] 2711 2711 <x:ref>accept-params</x:ref> = OWS ";" OWS "q=" qvalue *accept-ext … … 2739 2739 ";" OWS parameter ) 2740 2740 <x:ref>media-type</x:ref> = type "/" subtype *( OWS ";" OWS parameter ) 2741 <x:ref>message-header</x:ref> = <message-header, defined in [Part1], Section 4.2>2741 <x:ref>message-header</x:ref> = <message-header, defined in [Part1], Section 3.2> 2742 2742 2743 2743 <x:ref>parameter</x:ref> = attribute "=" value 2744 <x:ref>partial-URI</x:ref> = <partial-URI, defined in [Part1], Section 2. 1>2744 <x:ref>partial-URI</x:ref> = <partial-URI, defined in [Part1], Section 2.3> 2745 2745 2746 2746 <x:ref>quoted-string</x:ref> = <quoted-string, defined in [Part1], Section 1.2.2> 2747 <x:ref>qvalue</x:ref> = <qvalue, defined in [Part1], Section 3.5>2747 <x:ref>qvalue</x:ref> = <qvalue, defined in [Part1], Section 6.4> 2748 2748 2749 2749 <x:ref>subtype</x:ref> = token -
draft-ietf-httpbis/latest/p4-conditional.html
r610 r628 467 467 <tr> 468 468 <td class="header left"></td> 469 <td class="header right">July 17, 2009</td>469 <td class="header right">July 27, 2009</td> 470 470 </tr> 471 471 </table> … … 603 603 </pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a> <a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3> 604 604 <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p> 605 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 3.2</a>>605 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a>> 606 606 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="entity.tags" href="#entity.tags">Entity Tags</a></h1> 607 607 <p id="rfc.section.2.p.1">Entity tags are used for comparing two or more entities from the same requested resource. HTTP/1.1 uses entity tags in the … … 1162 1162 <a href="#header.etag" class="smpl">ETag-v</a> = entity-tag 1163 1163 1164 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 3.2>1164 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 6.1> 1165 1165 1166 1166 <a href="#header.if-match" class="smpl">If-Match</a> = "If-Match:" OWS If-Match-v … … 1328 1328 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a></li> 1329 1329 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a></li> 1330 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1.5">1.2.2</a></li>1330 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part1.5">1.2.2</a></li> 1331 1331 <li class="indline1"><em>Section 8.3.1</em> <a class="iref" href="#rfc.xref.Part1.6">3.1</a></li> 1332 1332 <li class="indline1"><em>Section 8.3</em> <a class="iref" href="#rfc.xref.Part1.7">3.1</a></li> -
draft-ietf-httpbis/latest/p4-conditional.xml
r610 r628 1400 1400 <x:ref>ETag-v</x:ref> = entity-tag 1401 1401 1402 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 3.2>1402 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 6.1> 1403 1403 1404 1404 <x:ref>If-Match</x:ref> = "If-Match:" OWS If-Match-v -
draft-ietf-httpbis/latest/p5-range.html
r620 r628 371 371 <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C"> 372 372 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 373 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.439, 2009-06-09 18:43:39, XSLT vendor: SAXON 8.9 .0.4from Saxonica http://www.saxonica.com/">373 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.439, 2009-06-09 18:43:39, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 374 374 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 375 375 <meta name="DC.Creator" content="Fielding, R."> … … 467 467 <tr> 468 468 <td class="header left"></td> 469 <td class="header right">July 2 4, 2009</td>469 <td class="header right">July 27, 2009</td> 470 470 </tr> 471 471 </table> … … 607 607 </pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a> <a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3> 608 608 <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p> 609 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 3.2</a>>609 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a>> 610 610 </pre><div id="rfc.figure.u.3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">entity-tag</a> = <entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#entity.tags" title="Entity Tags">Section 2</a>> 611 611 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="range.units" href="#range.units">Range Units</a></h1> … … 1111 1111 <a href="#header.content-range" class="smpl">Content-Range-v</a> = content-range-spec 1112 1112 1113 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 3.2>1113 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 6.1> 1114 1114 1115 1115 <a href="#header.if-range" class="smpl">If-Range</a> = "If-Range:" OWS If-Range-v … … 1156 1156 1157 1157 <a href="#core.rules" class="smpl">token</a> = <token, defined in [Part1], Section 1.2.2> 1158 1159 1160 1158 </pre> <div id="rfc.figure.u.26"></div> 1161 1159 <p>ABNF diagnostics:</p><pre class="inline">; Accept-Ranges defined but not used … … 1319 1317 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a></li> 1320 1318 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a></li> 1321 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1.5">1.2.2</a></li>1319 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part1.5">1.2.2</a></li> 1322 1320 </ul> 1323 1321 </li> -
draft-ietf-httpbis/latest/p5-range.xml
r618 r628 1409 1409 <x:ref>Content-Range-v</x:ref> = content-range-spec 1410 1410 1411 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 3.2>1411 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 6.1> 1412 1412 1413 1413 <x:ref>If-Range</x:ref> = "If-Range:" OWS If-Range-v … … 1454 1454 1455 1455 <x:ref>token</x:ref> = <token, defined in [Part1], Section 1.2.2> 1456 1457 1458 1456 </artwork> 1459 1457 </figure> -
draft-ietf-httpbis/latest/p6-cache.html
r616 r628 473 473 <tr> 474 474 <td class="header left"></td> 475 <td class="header right">July 2 4, 2009</td>475 <td class="header right">July 27, 2009</td> 476 476 </tr> 477 477 </table> … … 692 692 </pre><h3 id="rfc.section.1.4.2"><a href="#rfc.section.1.4.2">1.4.2</a> <a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3> 693 693 <p id="rfc.section.1.4.2.p.1">The ABNF rules below are defined in other parts:</p> 694 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">field-name</a> = <field-name, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</a>>695 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 3.2</a>>696 <a href="#abnf.dependencies" class="smpl">port</a> = <port, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2. 1</a>>694 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">field-name</a> = <field-name, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#message.headers" title="Message Headers">Section 3.2</a>> 695 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a>> 696 <a href="#abnf.dependencies" class="smpl">port</a> = <port, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.3</a>> 697 697 <a href="#abnf.dependencies" class="smpl">pseudonym</a> = <pseudonym, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a>> 698 <a href="#abnf.dependencies" class="smpl">uri-host</a> = <uri-host, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2. 1</a>>698 <a href="#abnf.dependencies" class="smpl">uri-host</a> = <uri-host, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.3</a>> 699 699 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="caching.overview" href="#caching.overview">Cache Operation</a></h1> 700 700 <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> <a id="response.cacheability" href="#response.cacheability">Response Cacheability</a></h2> … … 923 923 <p id="rfc.section.2.6.p.2">The selecting request-headers from two requests are defined to match if and only if the selecting request-headers in the first 924 924 request can be transformed to the selecting request-headers in the second request by adding or removing linear white space <span class="comment" id="rfc.comment.9">[<a href="#rfc.comment.9" class="smpl">rfc.comment.9</a>: [ref]]</span> at places where this is allowed by the corresponding ABNF, and/or combining multiple message-header fields with the same field 925 name following the rules about message headers in <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.925 name following the rules about message headers in <a href="p1-messaging.html#message.headers" title="Message Headers">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 926 926 </p> 927 927 <p id="rfc.section.2.6.p.3">If a header field is absent from a request, it can only match another request if it is also absent there.</p> … … 1190 1190 that time. 1191 1191 </p> 1192 <p id="rfc.section.3.3.p.3">The field-value is an absolute date and time as defined by HTTP-date in <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.1192 <p id="rfc.section.3.3.p.3">The field-value is an absolute date and time as defined by HTTP-date in <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format. 1193 1193 </p> 1194 1194 <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span> <a href="#header.expires" class="smpl">Expires</a> = "Expires" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.expires" class="smpl">Expires-v</a> … … 1569 1569 <a href="#header.expires" class="smpl">Expires-v</a> = HTTP-date 1570 1570 1571 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 3.2>1571 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 6.1> 1572 1572 1573 1573 <a href="#core.rules" class="smpl">OWS</a> = <OWS, defined in [Part1], Section 1.2.2> … … 1602 1602 <a href="#header.pragma" class="smpl">extension-pragma</a> = token [ "=" ( token / quoted-string ) ] 1603 1603 1604 <a href="#abnf.dependencies" class="smpl">field-name</a> = <field-name, defined in [Part1], Section 4.2>1605 1606 <a href="#abnf.dependencies" class="smpl">port</a> = <port, defined in [Part1], Section 2. 1>1604 <a href="#abnf.dependencies" class="smpl">field-name</a> = <field-name, defined in [Part1], Section 3.2> 1605 1606 <a href="#abnf.dependencies" class="smpl">port</a> = <port, defined in [Part1], Section 2.3> 1607 1607 <a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / extension-pragma 1608 1608 <a href="#abnf.dependencies" class="smpl">pseudonym</a> = <pseudonym, defined in [Part1], Section 8.9> … … 1612 1612 <a href="#core.rules" class="smpl">token</a> = <token, defined in [Part1], Section 1.2.2> 1613 1613 1614 <a href="#abnf.dependencies" class="smpl">uri-host</a> = <uri-host, defined in [Part1], Section 2. 1>1614 <a href="#abnf.dependencies" class="smpl">uri-host</a> = <uri-host, defined in [Part1], Section 2.3> 1615 1615 1616 1616 <a href="#header.warning" class="smpl">warn-agent</a> = ( uri-host [ ":" port ] ) / pseudonym … … 1620 1620 <a href="#header.warning" class="smpl">warning-value</a> = warn-code SP warn-agent SP warn-text [ SP warn-date 1621 1621 ] 1622 1623 1624 1622 </pre> <div id="rfc.figure.u.19"></div> 1625 1623 <p>ABNF diagnostics:</p><pre class="inline">; Age defined but not used … … 1870 1868 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.1">1.4</a></li> 1871 1869 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.4.1</a></li> 1872 <li class="indline1"><em>Section 2. 1</em> <a class="iref" href="#rfc.xref.Part1.8">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.4.2</a></li>1873 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1. 7">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.13">3.3</a></li>1874 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part1.6">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.12">2.6</a></li>1870 <li class="indline1"><em>Section 2.3</em> <a class="iref" href="#rfc.xref.Part1.8">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.4.2</a></li> 1871 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1.6">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.12">2.6</a></li> 1872 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part1.7">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.13">3.3</a></li> 1875 1873 <li class="indline1"><em>Section 8.3</em> <a class="iref" href="#rfc.xref.Part1.11">2.3.2</a></li> 1876 1874 <li class="indline1"><em>Section 8.9</em> <a class="iref" href="#rfc.xref.Part1.9">1.4.2</a></li> -
draft-ietf-httpbis/latest/p6-cache.xml
r615 r628 2137 2137 <x:ref>Expires-v</x:ref> = HTTP-date 2138 2138 2139 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 3.2>2139 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 6.1> 2140 2140 2141 2141 <x:ref>OWS</x:ref> = <OWS, defined in [Part1], Section 1.2.2> … … 2170 2170 <x:ref>extension-pragma</x:ref> = token [ "=" ( token / quoted-string ) ] 2171 2171 2172 <x:ref>field-name</x:ref> = <field-name, defined in [Part1], Section 4.2>2173 2174 <x:ref>port</x:ref> = <port, defined in [Part1], Section 2. 1>2172 <x:ref>field-name</x:ref> = <field-name, defined in [Part1], Section 3.2> 2173 2174 <x:ref>port</x:ref> = <port, defined in [Part1], Section 2.3> 2175 2175 <x:ref>pragma-directive</x:ref> = "no-cache" / extension-pragma 2176 2176 <x:ref>pseudonym</x:ref> = <pseudonym, defined in [Part1], Section 8.9> … … 2180 2180 <x:ref>token</x:ref> = <token, defined in [Part1], Section 1.2.2> 2181 2181 2182 <x:ref>uri-host</x:ref> = <uri-host, defined in [Part1], Section 2. 1>2182 <x:ref>uri-host</x:ref> = <uri-host, defined in [Part1], Section 2.3> 2183 2183 2184 2184 <x:ref>warn-agent</x:ref> = ( uri-host [ ":" port ] ) / pseudonym … … 2188 2188 <x:ref>warning-value</x:ref> = warn-code SP warn-agent SP warn-text [ SP warn-date 2189 2189 ] 2190 2191 2192 2190 </artwork> 2193 2191 </figure> -
draft-ietf-httpbis/latest/p7-auth.html
r609 r628 462 462 <tr> 463 463 <td class="header left"></td> 464 <td class="header right">July 13, 2009</td>464 <td class="header right">July 27, 2009</td> 465 465 </tr> 466 466 </table> … … 832 832 <a href="#abnf.dependencies" class="smpl">challenge</a> = <challenge, defined in [RFC2617], Section 1.2> 833 833 <a href="#abnf.dependencies" class="smpl">credentials</a> = <credentials, defined in [RFC2617], Section 1.2> 834 835 836 834 </pre> <div id="rfc.figure.u.8"></div> 837 835 <p>ABNF diagnostics:</p><pre class="inline">; Authorization defined but not used -
draft-ietf-httpbis/latest/p7-auth.xml
r609 r628 842 842 <x:ref>challenge</x:ref> = <challenge, defined in [RFC2617], Section 1.2> 843 843 <x:ref>credentials</x:ref> = <credentials, defined in [RFC2617], Section 1.2> 844 845 846 844 </artwork> 847 845 </figure>
Note: See TracChangeset
for help on using the changeset viewer.
