![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 678 for draft-ietf-httpbis
- Timestamp:
- Aug 13, 2009, 1:19:31 AM (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 12 edited
-
p1-messaging.html (modified) (4 diffs)
-
p2-semantics.html (modified) (19 diffs)
-
p2-semantics.xml (modified) (3 diffs)
-
p3-payload.html (modified) (22 diffs)
-
p3-payload.xml (modified) (3 diffs)
-
p4-conditional.html (modified) (8 diffs)
-
p4-conditional.xml (modified) (1 diff)
-
p5-range.html (modified) (7 diffs)
-
p5-range.xml (modified) (1 diff)
-
p6-cache.html (modified) (11 diffs)
-
p6-cache.xml (modified) (2 diffs)
-
p7-auth.html (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r677 r678 400 400 <meta name="DC.Creator" content="Reschke, J. F."> 401 401 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 402 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-1 2">402 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-13"> 403 403 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 404 404 <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> … … 431 431 </tr> 432 432 <tr> 433 <td class="header left">Expires: February 1 3, 2010</td>433 <td class="header left">Expires: February 14, 2010</td> 434 434 <td class="header right">HP</td> 435 435 </tr> … … 484 484 <tr> 485 485 <td class="header left"></td> 486 <td class="header right">August 1 2, 2009</td>486 <td class="header right">August 13, 2009</td> 487 487 </tr> 488 488 </table> … … 508 508 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 509 509 </p> 510 <p>This Internet-Draft will expire in February 1 3, 2010.</p>510 <p>This Internet-Draft will expire in February 14, 2010.</p> 511 511 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 512 512 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p2-semantics.html
r675 r678 399 399 <meta name="DC.Creator" content="Reschke, J. F."> 400 400 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 401 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-1 2">401 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-13"> 402 402 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 403 403 <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields."> … … 435 435 </tr> 436 436 <tr> 437 <td class="header left">Expires: February 1 3, 2010</td>437 <td class="header left">Expires: February 14, 2010</td> 438 438 <td class="header right">H. Frystyk</td> 439 439 </tr> … … 484 484 <tr> 485 485 <td class="header left"></td> 486 <td class="header right">August 1 2, 2009</td>486 <td class="header right">August 13, 2009</td> 487 487 </tr> 488 488 </table> … … 508 508 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 509 509 </p> 510 <p>This Internet-Draft will expire in February 1 3, 2010.</p>510 <p>This Internet-Draft will expire in February 14, 2010.</p> 511 511 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 512 512 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 714 714 <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.6</a>> 715 715 <a href="#abnf.dependencies" class="smpl">Host</a> = <Host, 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.6</a>> 716 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, 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#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 2.10.1</a>>716 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, 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#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a>> 717 717 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, 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#uri" title="Uniform Resource Identifiers">Section 2.6</a>> 718 <a href="#abnf.dependencies" class="smpl">product</a> = <product, 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#product.tokens" title="Product Tokens">Section 2.10.3</a>>719 <a href="#abnf.dependencies" class="smpl">TE</a> = <TE, 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#header.upgrade" title="Upgrade">Section 3.8</a>>718 <a href="#abnf.dependencies" class="smpl">product</a> = <product, 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#product.tokens" title="Product Tokens">Section 6.3</a>> 719 <a href="#abnf.dependencies" class="smpl">TE</a> = <TE, 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#header.upgrade" title="Upgrade">Section 9.8</a>> 720 720 <a href="#abnf.dependencies" class="smpl">URI</a> = <URI, 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#uri" title="Uniform Resource Identifiers">Section 2.6</a>> 721 721 </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>> … … 789 789 / <a href="#header.expect" class="smpl">Expect</a> ; <a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section 9.2</a> 790 790 / <a href="#header.from" class="smpl">From</a> ; <a href="#header.from" id="rfc.xref.header.from.1" title="From">Section 9.3</a> 791 / <a href="#abnf.dependencies" class="smpl">Host</a> ; <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.host" title="Host">Section 3.4</a>791 / <a href="#abnf.dependencies" class="smpl">Host</a> ; <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.host" title="Host">Section 9.4</a> 792 792 / <a href="#abnf.dependencies" class="smpl">If-Match</a> ; <a href="#Part4" id="rfc.xref.Part4.6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-match" title="If-Match">Section 6.2</a> 793 793 / <a href="#abnf.dependencies" class="smpl">If-Modified-Since</a> ; <a href="#Part4" id="rfc.xref.Part4.7"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 6.3</a> … … 799 799 / <a href="#abnf.dependencies" class="smpl">Range</a> ; <a href="#Part5" id="rfc.xref.Part5.5"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.range" title="Range">Section 5.4</a> 800 800 / <a href="#header.referer" class="smpl">Referer</a> ; <a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section 9.6</a> 801 / <a href="#abnf.dependencies" class="smpl">TE</a> ; <a href="#Part1" id="rfc.xref.Part1.18"><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 3.8</a>801 / <a href="#abnf.dependencies" class="smpl">TE</a> ; <a href="#Part1" id="rfc.xref.Part1.18"><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 9.8</a> 802 802 / <a href="#header.user-agent" class="smpl">User-Agent</a> ; <a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section 9.9</a> 803 803 </pre><p id="rfc.section.3.p.3">Request-header field names can be extended reliably only in combination with a change in the protocol version. However, new … … 894 894 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>. 895 895 </p> 896 <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 2.7.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 ensure896 <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 897 897 safe and proper transfer of the message. 898 898 </p> … … 1052 1052 </p> 1053 1053 <p id="rfc.section.7.8.p.2">TRACE allows the client to see what is being received at the other end of the request chain and use that data for testing 1054 or diagnostic information. The value of the Via header field (<a href="p1-messaging.html#header.via" title="Via">Section 3.9</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the1054 or diagnostic information. The value of the Via header field (<a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the 1055 1055 client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding messages in an 1056 1056 infinite loop. 1057 1057 </p> 1058 <p id="rfc.section.7.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> contain the entire request message in the entity-body, with a Content-Type of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Responses to this method <em class="bcp14">MUST NOT</em> be cached.1058 <p id="rfc.section.7.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> contain the entire request message in the entity-body, with a Content-Type of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 10.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Responses to this method <em class="bcp14">MUST NOT</em> be cached. 1059 1059 </p> 1060 1060 <div id="rfc.iref.c.1"></div> … … 1083 1083 <p id="rfc.section.8.1.1.p.1">The client <em class="bcp14">SHOULD</em> continue with its request. This interim response is used to inform the client that the initial part of the request has been 1084 1084 received and has not yet been rejected by the server. The client <em class="bcp14">SHOULD</em> continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The 1085 server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 2.11.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code.1085 server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code. 1086 1086 </p> 1087 1087 <div id="rfc.iref.26"></div> … … 1510 1510 </p> 1511 1511 <p id="rfc.section.9.2.p.7">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header.</p> 1512 <p id="rfc.section.9.2.p.8">See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 2.11.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status.1512 <p id="rfc.section.9.2.p.8">See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status. 1513 1513 </p> 1514 1514 <div id="rfc.iref.f.1"></div> … … 1612 1612 <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> 1613 1613 <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. 1614 The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 2.10.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 significance1614 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 1615 1615 for identifying the application. 1616 1616 </p> … … 1620 1620 </pre><p id="rfc.section.9.8.p.3">Example:</p> 1621 1621 <div id="rfc.figure.u.26"></div><pre class="text"> Server: CERN/3.0 libwww/2.17 1622 </pre><p id="rfc.section.9.8.p.5">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server response-header. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 3.9</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).1622 </pre><p id="rfc.section.9.8.p.5">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server response-header. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). 1623 1623 </p> 1624 1624 <div class="note"> … … 1633 1633 <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 1634 1634 purposes, the tracing of protocol violations, and automated recognition of user agents for the sake of tailoring responses 1635 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 2.10.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, the1635 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 1636 1636 product tokens are listed in order of their significance for identifying the application. 1637 1637 </p> … … 2261 2261 </p> 2262 2262 <p id="rfc.section.A.2.p.8">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly 2263 in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 3.9</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 9.8</a>)2263 in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 9.8</a>) 2264 2264 </p> 2265 2265 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> … … 2281 2281 <a href="#header.from" class="smpl">From-v</a> = mailbox 2282 2282 2283 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 2.10.1>2283 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 6.1> 2284 2284 <a href="#abnf.dependencies" class="smpl">Host</a> = <Host, defined in [Part1], Section 2.6> 2285 2285 … … 2331 2331 "505" / extension-code 2332 2332 2333 <a href="#abnf.dependencies" class="smpl">TE</a> = <TE, defined in [Part1], Section 3.8>2333 <a href="#abnf.dependencies" class="smpl">TE</a> = <TE, defined in [Part1], Section 9.8> 2334 2334 2335 2335 <a href="#abnf.dependencies" class="smpl">URI</a> = <URI, defined in [Part1], Section 2.6> … … 2360 2360 2361 2361 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in [Part1], Section 2.6> 2362 <a href="#abnf.dependencies" class="smpl">product</a> = <product, defined in [Part1], Section 2.10.3>2362 <a href="#abnf.dependencies" class="smpl">product</a> = <product, defined in [Part1], Section 6.3> 2363 2363 2364 2364 <a href="#core.rules" class="smpl">quoted-string</a> = <quoted-string, defined in [Part1], Section 1.2.2> … … 2693 2693 <li class="indline1"><em>Section 2.5</em> <a class="iref" href="#rfc.xref.Part1.23">8.5.6</a></li> 2694 2694 <li class="indline1"><em>Section 2.6</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.13">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.16">1.2.2</a></li> 2695 <li class="indline1"><em>Section 2.7.3</em> <a class="iref" href="#rfc.xref.Part1.19">6</a></li>2696 <li class="indline1"><em>Section 2.10.1</em> <a class="iref" href="#rfc.xref.Part1.12">1.2.2</a></li>2697 <li class="indline1"><em>Section 2.10.3</em> <a class="iref" href="#rfc.xref.Part1.14">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>2698 <li class="indline1"><em>Section 2.11.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>2699 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.Part1.17">3</a></li>2700 <li class="indline1"><em>Section 3.8</em> <a class="iref" href="#rfc.xref.Part1.15">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.18">3</a></li>2701 <li class="indline1"><em>Section 3.9</em> <a class="iref" href="#rfc.xref.Part1.20">7.8</a>, <a class="iref" href="#rfc.xref.Part1.26">9.8</a>, <a class="iref" href="#rfc.xref.Part1.28">A.2</a></li>2702 <li class="indline1"><em>Section 4.3.1</em> <a class="iref" href="#rfc.xref.Part1.21">7.8</a></li>2695 <li class="indline1"><em>Section 3.3</em> <a class="iref" href="#rfc.xref.Part1.19">6</a></li> 2696 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part1.12">1.2.2</a></li> 2697 <li class="indline1"><em>Section 6.3</em> <a class="iref" href="#rfc.xref.Part1.14">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> 2698 <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> 2699 <li class="indline1"><em>Section 9.4</em> <a class="iref" href="#rfc.xref.Part1.17">3</a></li> 2700 <li class="indline1"><em>Section 9.8</em> <a class="iref" href="#rfc.xref.Part1.15">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.18">3</a></li> 2701 <li class="indline1"><em>Section 9.9</em> <a class="iref" href="#rfc.xref.Part1.20">7.8</a>, <a class="iref" href="#rfc.xref.Part1.26">9.8</a>, <a class="iref" href="#rfc.xref.Part1.28">A.2</a></li> 2702 <li class="indline1"><em>Section 10.3.1</em> <a class="iref" href="#rfc.xref.Part1.21">7.8</a></li> 2703 2703 </ul> 2704 2704 </li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r672 r678 3262 3262 <x:ref>From-v</x:ref> = mailbox 3263 3263 3264 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 2.10.1>3264 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 6.1> 3265 3265 <x:ref>Host</x:ref> = <Host, defined in [Part1], Section 2.6> 3266 3266 … … 3312 3312 "505" / extension-code 3313 3313 3314 <x:ref>TE</x:ref> = <TE, defined in [Part1], Section 3.8>3314 <x:ref>TE</x:ref> = <TE, defined in [Part1], Section 9.8> 3315 3315 3316 3316 <x:ref>URI</x:ref> = <URI, defined in [Part1], Section 2.6> … … 3341 3341 3342 3342 <x:ref>partial-URI</x:ref> = <partial-URI, defined in [Part1], Section 2.6> 3343 <x:ref>product</x:ref> = <product, defined in [Part1], Section 2.10.3>3343 <x:ref>product</x:ref> = <product, defined in [Part1], Section 6.3> 3344 3344 3345 3345 <x:ref>quoted-string</x:ref> = <quoted-string, defined in [Part1], Section 1.2.2> -
draft-ietf-httpbis/latest/p3-payload.html
r675 r678 407 407 <meta name="DC.Creator" content="Reschke, J. F."> 408 408 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 409 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-1 2">409 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-13"> 410 410 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 411 411 <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> … … 438 438 </tr> 439 439 <tr> 440 <td class="header left">Expires: February 1 3, 2010</td>440 <td class="header left">Expires: February 14, 2010</td> 441 441 <td class="header right">HP</td> 442 442 </tr> … … 491 491 <tr> 492 492 <td class="header left"></td> 493 <td class="header right">August 1 2, 2009</td>493 <td class="header right">August 13, 2009</td> 494 494 </tr> 495 495 </table> … … 515 515 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 516 516 </p> 517 <p>This Internet-Draft will expire in February 1 3, 2010.</p>517 <p>This Internet-Draft will expire in February 14, 2010.</p> 518 518 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 519 519 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 704 704 <p id="rfc.section.1.3.2.p.1">The ABNF rules below are defined in other parts:</p> 705 705 <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.6</a>> 706 <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 3.2</a>>707 <a href="#abnf.dependencies" class="smpl">header-field</a> = <header-field, 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#header.fields" title="Header Fields">Section 2.7.2</a>>706 <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 9.2</a>> 707 <a href="#abnf.dependencies" class="smpl">header-field</a> = <header-field, 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#header.fields" title="Header Fields">Section 3.2</a>> 708 708 <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.6</a>> 709 <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 2.10.4</a>>709 <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>> 710 710 </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>> 711 711 </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>> … … 762 762 </p> 763 763 <dl class="empty"> 764 <dd>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 2.10.2.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.764 <dd>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 6.2.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 765 765 </dd> 766 766 </dl> … … 768 768 </p> 769 769 <dl class="empty"> 770 <dd>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 2.10.2.2.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>.770 <dd>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 6.2.2.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>. 771 771 </dd> 772 772 </dl> … … 774 774 </p> 775 775 <dl class="empty"> 776 <dd>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 2.10.2.2.3</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>.776 <dd>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 6.2.2.3</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>. 777 777 </dd> 778 778 </dl> … … 888 888 <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span> <a href="#entity.header.fields" class="smpl">entity-header</a> = <a href="#header.content-encoding" class="smpl">Content-Encoding</a> ; <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section 5.5</a> 889 889 / <a href="#header.content-language" class="smpl">Content-Language</a> ; <a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section 5.6</a> 890 / <a href="#abnf.dependencies" class="smpl">Content-Length</a> ; <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#header.content-length" title="Content-Length">Section 3.2</a>890 / <a href="#abnf.dependencies" class="smpl">Content-Length</a> ; <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#header.content-length" title="Content-Length">Section 9.2</a> 891 891 / <a href="#header.content-location" class="smpl">Content-Location</a> ; <a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section 5.7</a> 892 892 / <a href="#header.content-md5" class="smpl">Content-MD5</a> ; <a href="#header.content-md5" id="rfc.xref.header.content-md5.1" title="Content-MD5">Section 5.8</a> … … 904 904 <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> 905 905 <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> 906 </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 2.7.3</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>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure906 </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.15"><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 907 907 safe and proper transfer of the message. 908 908 </p> … … 919 919 </p> 920 920 <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> 921 <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 2.7.4</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> defines how the transfer-length of a message-body is determined.921 <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.16"><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. 922 922 </p> 923 923 <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1> … … 1028 1028 <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 1029 1029 "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user 1030 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 2.10.4</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1.1030 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.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1. 1031 1031 </p> 1032 1032 <div class="note"> … … 1152 1152 <ol> 1153 1153 <li>If the content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable, unless it 1154 is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 2.10.4</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable.")1154 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.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable.") 1155 1155 </li> 1156 1156 <li>The special "*" symbol in an Accept-Encoding field matches any available content-coding not explicitly listed in the header … … 1471 1471 <td>compress</td> 1472 1472 <td>UNIX "compress" program method</td> 1473 <td> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 2.10.2.2.1</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>1473 <td> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 6.2.2.1</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> 1474 1474 </td> 1475 1475 </tr> … … 1478 1478 <td>"zlib" format <a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a> with "deflate" compression 1479 1479 </td> 1480 <td> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 2.10.2.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>1480 <td> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 6.2.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 1481 1481 </td> 1482 1482 </tr> … … 1484 1484 <td>gzip</td> 1485 1485 <td>Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td> 1486 <td> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 2.10.2.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>1486 <td> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 6.2.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 1487 1487 </td> 1488 1488 </tr> … … 1740 1740 </p> 1741 1741 <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> 1742 <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 2.10.1</a> of <a href="#Part1" id="rfc.xref.Part1.22"><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.1742 <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.22"><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. 1743 1743 </p> 1744 1744 <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> … … 1757 1757 </p> 1758 1758 <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a> <a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h2> 1759 <p id="rfc.section.A.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 3.7</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>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol.1759 <p id="rfc.section.A.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 9.7</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>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol. 1760 1760 </p> 1761 1761 <h2 id="rfc.section.A.7"><a href="#rfc.section.A.7">A.7</a> <a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2> … … 1840 1840 <a href="#header.content-language" class="smpl">Content-Language-v</a> = *( "," OWS ) language-tag *( OWS "," [ OWS 1841 1841 language-tag ] ) 1842 <a href="#abnf.dependencies" class="smpl">Content-Length</a> = <Content-Length, defined in [Part1], Section 3.2>1842 <a href="#abnf.dependencies" class="smpl">Content-Length</a> = <Content-Length, defined in [Part1], Section 9.2> 1843 1843 <a href="#header.content-location" class="smpl">Content-Location</a> = "Content-Location:" OWS Content-Location-v 1844 1844 <a href="#header.content-location" class="smpl">Content-Location-v</a> = absolute-URI / partial-URI … … 1884 1884 <a href="#content-disposition" class="smpl">filename-parm</a> = "filename=" quoted-string 1885 1885 1886 <a href="#abnf.dependencies" class="smpl">header-field</a> = <header-field, defined in [Part1], Section 2.7.2>1886 <a href="#abnf.dependencies" class="smpl">header-field</a> = <header-field, defined in [Part1], Section 3.2> 1887 1887 1888 1888 <a href="#header.accept-language" class="smpl">language-range</a> = <language-range, defined in [RFC4647], Section 2.1> … … 1897 1897 1898 1898 <a href="#core.rules" class="smpl">quoted-string</a> = <quoted-string, defined in [Part1], Section 1.2.2> 1899 <a href="#abnf.dependencies" class="smpl">qvalue</a> = <qvalue, defined in [Part1], Section 2.10.4>1899 <a href="#abnf.dependencies" class="smpl">qvalue</a> = <qvalue, defined in [Part1], Section 6.4> 1900 1900 1901 1901 <a href="#media.types" class="smpl">subtype</a> = token … … 2180 2180 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.3.1</a></li> 2181 2181 <li class="indline1"><em>Section 2.6</em> <a class="iref" href="#rfc.xref.Part1.6">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.3.2</a></li> 2182 <li class="indline1"><em>Section 2.7.2</em> <a class="iref" href="#rfc.xref.Part1.8">1.3.2</a></li>2183 <li class="indline1"><em>Section 2.7.3</em> <a class="iref" href="#rfc.xref.Part1.15">3.2</a></li>2184 <li class="indline1"><em>Section 2.7.4</em> <a class="iref" href="#rfc.xref.Part1.16">3.2.2</a></li>2185 <li class="indline1"><em>Section 2.10.1</em> <a class="iref" href="#rfc.xref.Part1.22">A.3</a></li>2186 <li class="indline1"><em>Section 2.10.2.2.1</em> <a class="iref" href="#rfc.xref.Part1.11">2.2</a>, <a class="iref" href="#rfc.xref.Part1.19">6.2</a></li>2187 <li class="indline1"><em>Section 2.10.2.2.2</em> <a class="iref" href="#rfc.xref.Part1.12">2.2</a>, <a class="iref" href="#rfc.xref.Part1.20">6.2</a></li>2188 <li class="indline1"><em>Section 2.10.2.2.3</em> <a class="iref" href="#rfc.xref.Part1.13">2.2</a>, <a class="iref" href="#rfc.xref.Part1.21">6.2</a></li>2189 <li class="indline1"><em>Section 2.10.4</em> <a class="iref" href="#rfc.xref.Part1.10">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.17">5.1</a>, <a class="iref" href="#rfc.xref.Part1.18">5.3</a></li>2190 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1.7">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.14">3.1</a></li>2191 <li class="indline1"><em>Section 3.7</em> <a class="iref" href="#rfc.xref.Part1.23">A.6</a></li>2182 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1.8">1.3.2</a></li> 2183 <li class="indline1"><em>Section 3.3</em> <a class="iref" href="#rfc.xref.Part1.15">3.2</a></li> 2184 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.Part1.16">3.2.2</a></li> 2185 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part1.22">A.3</a></li> 2186 <li class="indline1"><em>Section 6.2.2.1</em> <a class="iref" href="#rfc.xref.Part1.11">2.2</a>, <a class="iref" href="#rfc.xref.Part1.19">6.2</a></li> 2187 <li class="indline1"><em>Section 6.2.2.2</em> <a class="iref" href="#rfc.xref.Part1.12">2.2</a>, <a class="iref" href="#rfc.xref.Part1.20">6.2</a></li> 2188 <li class="indline1"><em>Section 6.2.2.3</em> <a class="iref" href="#rfc.xref.Part1.13">2.2</a>, <a class="iref" href="#rfc.xref.Part1.21">6.2</a></li> 2189 <li class="indline1"><em>Section 6.4</em> <a class="iref" href="#rfc.xref.Part1.10">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.17">5.1</a>, <a class="iref" href="#rfc.xref.Part1.18">5.3</a></li> 2190 <li class="indline1"><em>Section 9.2</em> <a class="iref" href="#rfc.xref.Part1.7">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.14">3.1</a></li> 2191 <li class="indline1"><em>Section 9.7</em> <a class="iref" href="#rfc.xref.Part1.23">A.6</a></li> 2192 2192 </ul> 2193 2193 </li> -
draft-ietf-httpbis/latest/p3-payload.xml
r673 r678 2780 2780 <x:ref>Content-Language-v</x:ref> = *( "," OWS ) language-tag *( OWS "," [ OWS 2781 2781 language-tag ] ) 2782 <x:ref>Content-Length</x:ref> = <Content-Length, defined in [Part1], Section 3.2>2782 <x:ref>Content-Length</x:ref> = <Content-Length, defined in [Part1], Section 9.2> 2783 2783 <x:ref>Content-Location</x:ref> = "Content-Location:" OWS Content-Location-v 2784 2784 <x:ref>Content-Location-v</x:ref> = absolute-URI / partial-URI … … 2824 2824 <x:ref>filename-parm</x:ref> = "filename=" quoted-string 2825 2825 2826 <x:ref>header-field</x:ref> = <header-field, defined in [Part1], Section 2.7.2>2826 <x:ref>header-field</x:ref> = <header-field, defined in [Part1], Section 3.2> 2827 2827 2828 2828 <x:ref>language-range</x:ref> = <language-range, defined in [RFC4647], Section 2.1> … … 2837 2837 2838 2838 <x:ref>quoted-string</x:ref> = <quoted-string, defined in [Part1], Section 1.2.2> 2839 <x:ref>qvalue</x:ref> = <qvalue, defined in [Part1], Section 2.10.4>2839 <x:ref>qvalue</x:ref> = <qvalue, defined in [Part1], Section 6.4> 2840 2840 2841 2841 <x:ref>subtype</x:ref> = token -
draft-ietf-httpbis/latest/p4-conditional.html
r675 r678 396 396 <meta name="DC.Creator" content="Reschke, J. F."> 397 397 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 398 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-1 2">398 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-13"> 399 399 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 400 400 <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests."> … … 427 427 </tr> 428 428 <tr> 429 <td class="header left">Expires: February 1 3, 2010</td>429 <td class="header left">Expires: February 14, 2010</td> 430 430 <td class="header right">HP</td> 431 431 </tr> … … 480 480 <tr> 481 481 <td class="header left"></td> 482 <td class="header right">August 1 2, 2009</td>482 <td class="header right">August 13, 2009</td> 483 483 </tr> 484 484 </table> … … 504 504 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 505 505 </p> 506 <p>This Internet-Draft will expire in February 1 3, 2010.</p>506 <p>This Internet-Draft will expire in February 14, 2010.</p> 507 507 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 508 508 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 616 616 </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> 617 617 <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p> 618 <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 2.10.1</a>>618 <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>> 619 619 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="entity.tags" href="#entity.tags">Entity Tags</a></h1> 620 620 <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 … … 643 643 <ul> 644 644 <li> 645 <p>Date, unless its omission is required by <a href="p1-messaging.html#clockless.origin.server.operation" title="Clockless Origin Server Operation">Section 3.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.645 <p>Date, unless its omission is required by <a href="p1-messaging.html#clockless.origin.server.operation" title="Clockless Origin Server Operation">Section 9.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 646 646 </p> 647 647 <p>If a clockless origin server obeys these rules, and proxies and clients add their own Date to any response received without 648 one (as already specified by <a href="p1-messaging.html#header.date" title="Date">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, caches will operate correctly.648 one (as already specified by <a href="p1-messaging.html#header.date" title="Date">Section 9.3</a> of <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, caches will operate correctly. 649 649 </p> 650 650 </li> … … 1173 1173 <a href="#header.etag" class="smpl">ETag-v</a> = entity-tag 1174 1174 1175 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 2.10.1>1175 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 6.1> 1176 1176 1177 1177 <a href="#header.if-match" class="smpl">If-Match</a> = "If-Match:" OWS If-Match-v … … 1343 1343 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a></li> 1344 1344 <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> 1345 <li class="indline1"><em>Section 2.10.1</em> <a class="iref" href="#rfc.xref.Part1.5">1.2.2</a></li>1346 <li class="indline1"><em>Section 3.3.1</em> <a class="iref" href="#rfc.xref.Part1.6">3.1</a></li>1347 <li class="indline1"><em>Section 3.3</em> <a class="iref" href="#rfc.xref.Part1.7">3.1</a></li>1345 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part1.5">1.2.2</a></li> 1346 <li class="indline1"><em>Section 9.3.1</em> <a class="iref" href="#rfc.xref.Part1.6">3.1</a></li> 1347 <li class="indline1"><em>Section 9.3</em> <a class="iref" href="#rfc.xref.Part1.7">3.1</a></li> 1348 1348 </ul> 1349 1349 </li> -
draft-ietf-httpbis/latest/p4-conditional.xml
r662 r678 1392 1392 <x:ref>ETag-v</x:ref> = entity-tag 1393 1393 1394 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 2.10.1>1394 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 6.1> 1395 1395 1396 1396 <x:ref>If-Match</x:ref> = "If-Match:" OWS If-Match-v -
draft-ietf-httpbis/latest/p5-range.html
r675 r678 396 396 <meta name="DC.Creator" content="Reschke, J. F."> 397 397 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 398 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-1 2">398 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-13"> 399 399 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 400 400 <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests."> … … 427 427 </tr> 428 428 <tr> 429 <td class="header left">Expires: February 1 3, 2010</td>429 <td class="header left">Expires: February 14, 2010</td> 430 430 <td class="header right">HP</td> 431 431 </tr> … … 480 480 <tr> 481 481 <td class="header left"></td> 482 <td class="header right">August 1 2, 2009</td>482 <td class="header right">August 13, 2009</td> 483 483 </tr> 484 484 </table> … … 504 504 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 505 505 </p> 506 <p>This Internet-Draft will expire in February 1 3, 2010.</p>506 <p>This Internet-Draft will expire in February 14, 2010.</p> 507 507 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 508 508 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 620 620 </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> 621 621 <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p> 622 <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 2.10.1</a>>622 <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>> 623 623 </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>> 624 624 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="range.units" href="#range.units">Range Units</a></h1> … … 1148 1148 <a href="#header.content-range" class="smpl">Content-Range-v</a> = content-range-spec 1149 1149 1150 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 2.10.1>1150 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 6.1> 1151 1151 1152 1152 <a href="#header.if-range" class="smpl">If-Range</a> = "If-Range:" OWS If-Range-v … … 1359 1359 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a></li> 1360 1360 <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> 1361 <li class="indline1"><em>Section 2.10.1</em> <a class="iref" href="#rfc.xref.Part1.5">1.2.2</a></li>1361 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part1.5">1.2.2</a></li> 1362 1362 </ul> 1363 1363 </li> -
draft-ietf-httpbis/latest/p5-range.xml
r662 r678 1439 1439 <x:ref>Content-Range-v</x:ref> = content-range-spec 1440 1440 1441 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 2.10.1>1441 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 6.1> 1442 1442 1443 1443 <x:ref>If-Range</x:ref> = "If-Range:" OWS If-Range-v -
draft-ietf-httpbis/latest/p6-cache.html
r675 r678 398 398 <meta name="DC.Creator" content="Reschke, J. F."> 399 399 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 400 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-1 2">400 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-13"> 401 401 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 402 402 <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 429 429 </tr> 430 430 <tr> 431 <td class="header left">Expires: February 1 3, 2010</td>431 <td class="header left">Expires: February 14, 2010</td> 432 432 <td class="header right">HP</td> 433 433 </tr> … … 486 486 <tr> 487 487 <td class="header left"></td> 488 <td class="header right">August 1 2, 2009</td>488 <td class="header right">August 13, 2009</td> 489 489 </tr> 490 490 </table> … … 510 510 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 511 511 </p> 512 <p>This Internet-Draft will expire in February 1 3, 2010.</p>512 <p>This Internet-Draft will expire in February 14, 2010.</p> 513 513 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 514 514 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 705 705 </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> 706 706 <p id="rfc.section.1.4.2.p.1">The ABNF rules below are defined in other parts:</p> 707 <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#header.fields" title="Header Fields">Section 2.7.2</a>>708 <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 2.10.1</a>>707 <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#header.fields" title="Header Fields">Section 3.2</a>> 708 <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>> 709 709 <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.6</a>> 710 <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 3.9</a>>710 <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 9.9</a>> 711 711 <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.6</a>> 712 712 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="caching.overview" href="#caching.overview">Cache Operation</a></h1> … … 831 831 <p id="rfc.section.2.3.2.p.2">The term "age_value" denotes the value of the Age header, in a form appropriate for arithmetic operations.</p> 832 832 <p id="rfc.section.2.3.2.p.3">HTTP/1.1 requires origin servers to send a Date header, if possible, with every response, giving the time at which the response 833 was generated (see <a href="p1-messaging.html#header.date" title="Date">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The term "date_value" denotes the value of the Date header, in a form appropriate for arithmetic operations.833 was generated (see <a href="p1-messaging.html#header.date" title="Date">Section 9.3</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The term "date_value" denotes the value of the Date header, in a form appropriate for arithmetic operations. 834 834 </p> 835 835 <p id="rfc.section.2.3.2.p.4">The term "now" means "the current value of the clock at the host performing the calculation." Hosts that use HTTP, but especially … … 936 936 <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 937 937 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 938 name following the rules about header fields in <a href="p1-messaging.html#header.fields" title="Header Fields">Section 2.7.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>.938 name following the rules about header fields in <a href="p1-messaging.html#header.fields" title="Header Fields">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>. 939 939 </p> 940 940 <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> … … 1203 1203 that time. 1204 1204 </p> 1205 <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 2.10.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.1205 <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. 1206 1206 </p> 1207 1207 <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> … … 1564 1564 <a href="#header.expires" class="smpl">Expires-v</a> = HTTP-date 1565 1565 1566 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 2.10.1>1566 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 6.1> 1567 1567 1568 1568 <a href="#core.rules" class="smpl">OWS</a> = <OWS, defined in [Part1], Section 1.2.2> … … 1597 1597 <a href="#header.pragma" class="smpl">extension-pragma</a> = token [ "=" ( token / quoted-string ) ] 1598 1598 1599 <a href="#abnf.dependencies" class="smpl">field-name</a> = <field-name, defined in [Part1], Section 2.7.2>1599 <a href="#abnf.dependencies" class="smpl">field-name</a> = <field-name, defined in [Part1], Section 3.2> 1600 1600 1601 1601 <a href="#abnf.dependencies" class="smpl">port</a> = <port, defined in [Part1], Section 2.6> 1602 1602 <a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / extension-pragma 1603 <a href="#abnf.dependencies" class="smpl">pseudonym</a> = <pseudonym, defined in [Part1], Section 3.9>1603 <a href="#abnf.dependencies" class="smpl">pseudonym</a> = <pseudonym, defined in [Part1], Section 9.9> 1604 1604 1605 1605 <a href="#core.rules" class="smpl">quoted-string</a> = <quoted-string, defined in [Part1], Section 1.2.2> … … 1864 1864 <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> 1865 1865 <li class="indline1"><em>Section 2.6</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> 1866 <li class="indline1"><em>Section 2.7.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>1867 <li class="indline1"><em>Section 2.10.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>1868 <li class="indline1"><em>Section 3.3</em> <a class="iref" href="#rfc.xref.Part1.11">2.3.2</a></li>1869 <li class="indline1"><em>Section 3.9</em> <a class="iref" href="#rfc.xref.Part1.9">1.4.2</a></li>1866 <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> 1867 <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> 1868 <li class="indline1"><em>Section 9.3</em> <a class="iref" href="#rfc.xref.Part1.11">2.3.2</a></li> 1869 <li class="indline1"><em>Section 9.9</em> <a class="iref" href="#rfc.xref.Part1.9">1.4.2</a></li> 1870 1870 </ul> 1871 1871 </li> -
draft-ietf-httpbis/latest/p6-cache.xml
r669 r678 2099 2099 <x:ref>Expires-v</x:ref> = HTTP-date 2100 2100 2101 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 2.10.1>2101 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 6.1> 2102 2102 2103 2103 <x:ref>OWS</x:ref> = <OWS, defined in [Part1], Section 1.2.2> … … 2132 2132 <x:ref>extension-pragma</x:ref> = token [ "=" ( token / quoted-string ) ] 2133 2133 2134 <x:ref>field-name</x:ref> = <field-name, defined in [Part1], Section 2.7.2>2134 <x:ref>field-name</x:ref> = <field-name, defined in [Part1], Section 3.2> 2135 2135 2136 2136 <x:ref>port</x:ref> = <port, defined in [Part1], Section 2.6> 2137 2137 <x:ref>pragma-directive</x:ref> = "no-cache" / extension-pragma 2138 <x:ref>pseudonym</x:ref> = <pseudonym, defined in [Part1], Section 3.9>2138 <x:ref>pseudonym</x:ref> = <pseudonym, defined in [Part1], Section 9.9> 2139 2139 2140 2140 <x:ref>quoted-string</x:ref> = <quoted-string, defined in [Part1], Section 1.2.2> -
draft-ietf-httpbis/latest/p7-auth.html
r675 r678 390 390 <meta name="DC.Creator" content="Reschke, J. F."> 391 391 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 392 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-1 2">392 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-13"> 393 393 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 394 394 <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication."> … … 426 426 </tr> 427 427 <tr> 428 <td class="header left">Expires: February 1 3, 2010</td>428 <td class="header left">Expires: February 14, 2010</td> 429 429 <td class="header right">H. Frystyk</td> 430 430 </tr> … … 475 475 <tr> 476 476 <td class="header left"></td> 477 <td class="header right">August 1 2, 2009</td>477 <td class="header right">August 13, 2009</td> 478 478 </tr> 479 479 </table> … … 499 499 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 500 500 </p> 501 <p>This Internet-Draft will expire in February 1 3, 2010.</p>501 <p>This Internet-Draft will expire in February 14, 2010.</p> 502 502 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 503 503 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
Note: See TracChangeset
for help on using the changeset viewer.
