Ignore:
Timestamp:
06/05/14 08:10:18 (6 years ago)
Author:
julian.reschke@…
Message:

insert RFC numbers (#553)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p4-conditional.html

    r2628 r2629  
    463463  }
    464464  @bottom-center {
    465        content: "Expires November 2, 2014";
     465       content: "Expires November 7, 2014";
    466466  }
    467467  @bottom-right {
     
    506506      <meta name="dct.creator" content="Reschke, J. F.">
    507507      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    508       <meta name="dct.issued" scheme="ISO8601" content="2014-05-01">
     508      <meta name="dct.issued" scheme="ISO8601" content="2014-05-06">
    509509      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    510510      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false.">
     
    532532            </tr>
    533533            <tr>
    534                <td class="left">Expires: November 2, 2014</td>
    535                <td class="right">May 1, 2014</td>
     534               <td class="left">Expires: November 7, 2014</td>
     535               <td class="right">May 6, 2014</td>
    536536            </tr>
    537537         </tbody>
     
    561561            in progress”.
    562562         </p>
    563          <p>This Internet-Draft will expire on November 2, 2014.</p>
     563         <p>This Internet-Draft will expire on November 7, 2014.</p>
    564564      </div>
    565565      <div id="rfc.copyrightnotice">
     
    644644      <div id="introduction">
    645645         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
    646          <p id="rfc.section.1.p.1">Conditional requests are HTTP requests <a href="#Part2" id="rfc.xref.Part2.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> that include one or more header fields indicating a precondition to be tested before applying the method semantics to the
     646         <p id="rfc.section.1.p.1">Conditional requests are HTTP requests <a href="#RFC7231" id="rfc.xref.RFC7231.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a> that include one or more header fields indicating a precondition to be tested before applying the method semantics to the
    647647            target resource. This document defines the HTTP/1.1 conditional request mechanisms in terms of the architecture, syntax notation,
    648             and conformance criteria defined in <a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    649          </p>
    650          <p id="rfc.section.1.p.2">Conditional GET requests are the most efficient mechanism for HTTP cache updates <a href="#Part6" id="rfc.xref.Part6.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>. Conditionals can also be applied to state-changing methods, such as PUT and DELETE, to prevent the "lost update" problem:
     648            and conformance criteria defined in <a href="#RFC7230" id="rfc.xref.RFC7230.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
     649         </p>
     650         <p id="rfc.section.1.p.2">Conditional GET requests are the most efficient mechanism for HTTP cache updates <a href="#RFC7234" id="rfc.xref.RFC7234.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>. Conditionals can also be applied to state-changing methods, such as PUT and DELETE, to prevent the "lost update" problem:
    651651            one client accidentally overwriting the work of another client that has been acting in parallel.
    652652         </p>
     
    654654            state as observed in a previously obtained representation (one value in that set). A resource might have multiple current
    655655            representations, each with its own observable state. The conditional request mechanisms assume that the mapping of requests
    656             to a "selected representation" (<a href="p2-semantics.html#representations" title="Representations">Section 3</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) will be consistent over time if the server intends to take advantage of conditionals. Regardless, if the mapping is inconsistent
     656            to a "selected representation" (<a href="p2-semantics.html#representations" title="Representations">Section 3</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>) will be consistent over time if the server intends to take advantage of conditionals. Regardless, if the mapping is inconsistent
    657657            and the server is unable to select the appropriate representation, then no harm will result when the precondition evaluates
    658658            to false.
     
    665665               in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    666666            </p>
    667             <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     667            <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    668668            </p>
    669669         </div>
    670670         <div id="notation">
    671671            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
    672             <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 7</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates
     672            <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates
    673673               repetition). <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;B</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected grammar with all list operators expanded to standard ABNF notation.
    674674            </p>
     
    748748               <h3 id="rfc.section.2.2.1"><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;<a href="#lastmod.generation">Generation</a></h3>
    749749               <p id="rfc.section.2.2.1.p.1">An origin server <em class="bcp14">SHOULD</em> send Last-Modified for any selected representation for which a last modification date can be reasonably and consistently determined,
    750                   since its use in conditional requests and evaluating cache freshness (<a href="#Part6" id="rfc.xref.Part6.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) results in a substantial reduction of HTTP traffic on the Internet and can be a significant factor in improving service
     750                  since its use in conditional requests and evaluating cache freshness (<a href="#RFC7234" id="rfc.xref.RFC7234.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>) results in a substantial reduction of HTTP traffic on the Internet and can be a significant factor in improving service
    751751                  scalability and reliability.
    752752               </p>
     
    847847               </p>
    848848               <p id="rfc.section.2.3.1.p.3">An origin server <em class="bcp14">SHOULD</em> send ETag for any selected representation for which detection of changes can be reasonably and consistently determined, since
    849                   the entity-tag's use in conditional requests and evaluating cache freshness (<a href="#Part6" id="rfc.xref.Part6.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) can result in a substantial reduction of HTTP network traffic and can be a significant factor in improving service scalability
     849                  the entity-tag's use in conditional requests and evaluating cache freshness (<a href="#RFC7234" id="rfc.xref.RFC7234.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>) can result in a substantial reduction of HTTP network traffic and can be a significant factor in improving service scalability
    850850                  and reliability.
    851851               </p>
     
    905905            <div id="example.entity.tag.vs.conneg">
    906906               <h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;<a href="#example.entity.tag.vs.conneg">Example: Entity-tags Varying on Content-Negotiated Resources</a></h3>
    907                <p id="rfc.section.2.3.3.p.1">Consider a resource that is subject to content negotiation (<a href="p2-semantics.html#content.negotiation" title="Content Negotiation">Section 3.4</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>), and where the representations sent in response to a GET request vary based on the <a href="p2-semantics.html#header.accept-encoding" class="smpl">Accept-Encoding</a> request header field (<a href="p2-semantics.html#header.accept-encoding" title="Accept-Encoding">Section 5.3.4</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>):
     907               <p id="rfc.section.2.3.3.p.1">Consider a resource that is subject to content negotiation (<a href="p2-semantics.html#content.negotiation" title="Content Negotiation">Section 3.4</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>), and where the representations sent in response to a GET request vary based on the <a href="p2-semantics.html#header.accept-encoding" class="smpl">Accept-Encoding</a> request header field (<a href="p2-semantics.html#header.accept-encoding" title="Accept-Encoding">Section 5.3.4</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>):
    908908               </p>
    909909               <div id="rfc.figure.u.5"></div>
     
    939939                  <p><b>Note:</b> Content codings are a property of the representation data, so a strong entity-tag for a content-encoded representation has
    940940                     to be distinct from the entity tag of an unencoded representation to prevent potential conflicts during cache updates and
    941                      range requests. In contrast, transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) apply only during message transfer and do not result in distinct entity-tags.
     941                     range requests. In contrast, transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>) apply only during message transfer and do not result in distinct entity-tags.
    942942                  </p>
    943943               </div>
     
    10291029            <p id="rfc.section.3.2.p.7">If-None-Match can also be used with a value of "*" to prevent an unsafe request method (e.g., PUT) from inadvertently modifying
    10301030               an existing representation of the target resource when the client believes that the resource does not have a current representation
    1031                (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 4.2.1</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). This is a variation on the "lost update" problem that might arise if more than one client attempts to create an initial
     1031               (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 4.2.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>). This is a variation on the "lost update" problem that might arise if more than one client attempts to create an initial
    10321032               representation for the target resource.
    10331033            </p>
     
    10381038            <p id="rfc.section.3.2.p.9">An origin server <em class="bcp14">MUST NOT</em> perform the requested method if the condition evaluates to false; instead, the origin server <em class="bcp14">MUST</em> respond with either a) the <a href="#status.304" class="smpl">304 (Not Modified)</a> status code if the request method is GET or HEAD; or, b) the <a href="#status.412" class="smpl">412 (Precondition Failed)</a> status code for all other request methods.
    10391039            </p>
    1040             <p id="rfc.section.3.2.p.10">Requirements on cache handling of a received If-None-Match header field are defined in <a href="p6-cache.html#validation.received" title="Handling a Received Validation Request">Section 4.3.2</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>.
     1040            <p id="rfc.section.3.2.p.10">Requirements on cache handling of a received If-None-Match header field are defined in <a href="p6-cache.html#validation.received" title="Handling a Received Validation Request">Section 4.3.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>.
    10411041            </p>
    10421042         </div>
     
    10751075               provided in the field-value; instead, the origin server <em class="bcp14">SHOULD</em> generate a <a href="#status.304" class="smpl">304 (Not Modified)</a> response, including only those metadata that are useful for identifying or updating a previously cached response.
    10761076            </p>
    1077             <p id="rfc.section.3.3.p.12">Requirements on cache handling of a received If-Modified-Since header field are defined in <a href="p6-cache.html#validation.received" title="Handling a Received Validation Request">Section 4.3.2</a> of <a href="#Part6" id="rfc.xref.Part6.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>.
     1077            <p id="rfc.section.3.3.p.12">Requirements on cache handling of a received If-Modified-Since header field are defined in <a href="p6-cache.html#validation.received" title="Handling a Received Validation Request">Section 4.3.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>.
    10781078            </p>
    10791079         </div>
     
    11121112            <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a href="#header.if-range">If-Range</a></h2>
    11131113            <p id="rfc.section.3.5.p.1">The "If-Range" header field provides a special conditional request mechanism that is similar to the <a href="#header.if-match" class="smpl">If-Match</a> and <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> header fields but instructs the recipient to ignore the <a href="p5-range.html#header.range" class="smpl">Range</a> header field if the validator doesn't match, resulting in transfer of the new selected representation instead of a 412 response.
    1114                If-Range is defined in <a href="p5-range.html#header.if-range" title="If-Range">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>.
     1114               If-Range is defined in <a href="p5-range.html#header.if-range" title="If-Range">Section 3.2</a> of <a href="#RFC7233" id="rfc.xref.RFC7233.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a>.
    11151115            </p>
    11161116         </div>
     
    11321132               cache updates (e.g., <a href="#header.last-modified" class="smpl">Last-Modified</a> might be useful if the response does not have an <a href="#header.etag" class="smpl">ETag</a> field).
    11331133            </p>
    1134             <p id="rfc.section.4.1.p.4">Requirements on a cache that receives a 304 response are defined in <a href="p6-cache.html#freshening.responses" title="Freshening Stored Responses upon Validation">Section 4.3.4</a> of <a href="#Part6" id="rfc.xref.Part6.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>. If the conditional request originated with an outbound client, such as a user agent with its own cache sending a conditional
     1134            <p id="rfc.section.4.1.p.4">Requirements on a cache that receives a 304 response are defined in <a href="p6-cache.html#freshening.responses" title="Freshening Stored Responses upon Validation">Section 4.3.4</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>. If the conditional request originated with an outbound client, such as a user agent with its own cache sending a conditional
    11351135               GET to a shared proxy, then the proxy <em class="bcp14">SHOULD</em> forward the 304 response to that client.
    11361136            </p>
     
    12051205            <li id="precedence5">When the method is GET and both <a href="p5-range.html#header.range" class="smpl">Range</a> and <a href="p5-range.html#header.if-range" class="smpl">If-Range</a> are present, evaluate the <a href="p5-range.html#header.if-range" class="smpl">If-Range</a> precondition:
    12061206               <ul>
    1207                   <li>if the validator matches and the Range specification is applicable to the selected representation, respond <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> <a href="#Part5" id="rfc.xref.Part5.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></li>
     1207                  <li>if the validator matches and the Range specification is applicable to the selected representation, respond <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> <a href="#RFC7233" id="rfc.xref.RFC7233.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a></li>
    12081208               </ul>
    12091209            </li>
     
    13221322         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
    13231323         <p id="rfc.section.8.p.1">This section is meant to inform developers, information providers, and users of known security concerns specific to the HTTP
    1324             conditional request mechanisms. More general security considerations are addressed in HTTP messaging <a href="#Part1" id="rfc.xref.Part1.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> and semantics <a href="#Part2" id="rfc.xref.Part2.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>.
     1324            conditional request mechanisms. More general security considerations are addressed in HTTP messaging <a href="#RFC7230" id="rfc.xref.RFC7230.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a> and semantics <a href="#RFC7231" id="rfc.xref.RFC7231.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>.
    13251325         </p>
    13261326         <p id="rfc.section.8.p.2">The validators defined by this specification are not intended to ensure the validity of a representation, guard against malicious
     
    13391339      <div id="acks">
    13401340         <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#acks">Acknowledgments</a></h1>
    1341          <p id="rfc.section.9.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     1341         <p id="rfc.section.9.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    13421342         </p>
    13431343      </div>
     
    13471347      </h2>
    13481348      <table>
    1349          <tr>
    1350             <td class="reference"><b id="Part1">[Part1]</b></td>
    1351             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), May&nbsp;2014.
    1352             </td>
    1353          </tr>
    1354          <tr>
    1355             <td class="reference"><b id="Part2">[Part2]</b></td>
    1356             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), May&nbsp;2014.
    1357             </td>
    1358          </tr>
    1359          <tr>
    1360             <td class="reference"><b id="Part5">[Part5]</b></td>
    1361             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), May&nbsp;2014.
    1362             </td>
    1363          </tr>
    1364          <tr>
    1365             <td class="reference"><b id="Part6">[Part6]</b></td>
    1366             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), May&nbsp;2014.
    1367             </td>
    1368          </tr>
    13691349         <tr>
    13701350            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
     
    13751355            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    13761356            <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
     1357            </td>
     1358         </tr>
     1359         <tr>
     1360            <td class="reference"><b id="RFC7230">[RFC7230]</b></td>
     1361            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), May&nbsp;2014.
     1362            </td>
     1363         </tr>
     1364         <tr>
     1365            <td class="reference"><b id="RFC7231">[RFC7231]</b></td>
     1366            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), May&nbsp;2014.
     1367            </td>
     1368         </tr>
     1369         <tr>
     1370            <td class="reference"><b id="RFC7233">[RFC7233]</b></td>
     1371            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), May&nbsp;2014.
     1372            </td>
     1373         </tr>
     1374         <tr>
     1375            <td class="reference"><b id="RFC7234">[RFC7234]</b></td>
     1376            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), May&nbsp;2014.
    13771377            </td>
    13781378         </tr>
     
    14171417            character).
    14181418         </p>
    1419          <p id="rfc.section.B.p.2">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>:
    1420          </p>
    1421          <div id="rfc.figure.u.16"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
    1422   <a href="#imported.abnf" class="smpl">obs-text</a>      = &lt;obs-text, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>&gt;
     1419         <p id="rfc.section.B.p.2">The rules below are defined in <a href="#RFC7230" id="rfc.xref.RFC7230.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>:
     1420         </p>
     1421         <div id="rfc.figure.u.16"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
     1422  <a href="#imported.abnf" class="smpl">obs-text</a>      = &lt;obs-text, defined in <a href="#RFC7230" id="rfc.xref.RFC7230.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>&gt;
    14231423</pre><p id="rfc.section.B.p.4">The rules below are defined in other parts:</p>
    1424          <div id="rfc.figure.u.17"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>&gt;
     1424         <div id="rfc.figure.u.17"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#RFC7231" id="rfc.xref.RFC7231.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>&gt;
    14251425</pre></div>
    14261426      <div id="collected.abnf">
    14271427         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
    1428          <p id="rfc.section.C.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     1428         <p id="rfc.section.C.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
    14291429         </p>
    14301430         <div id="rfc.figure.u.18"></div><pre class="inline"><a href="#header.etag" class="smpl">ETag</a> = entity-tag
    14311431
    1432 <a href="#imported.abnf" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part2], Section 7.1.1.1&gt;
     1432<a href="#imported.abnf" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [RFC7231], Section 7.1.1.1&gt;
    14331433
    14341434<a href="#header.if-match" class="smpl">If-Match</a> = "*" / ( *( "," OWS ) entity-tag *( OWS "," [ OWS
     
    14411441<a href="#header.last-modified" class="smpl">Last-Modified</a> = HTTP-date
    14421442
    1443 <a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.3&gt;
     1443<a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, defined in [RFC7230], Section 3.2.3&gt;
    14441444
    14451445<a href="#header.etag" class="smpl">entity-tag</a> = [ weak ] opaque-tag
     
    14471447 / obs-text
    14481448
    1449 <a href="#imported.abnf" class="smpl">obs-text</a> = &lt;obs-text, defined in [Part1], Section 3.2.6&gt;
     1449<a href="#imported.abnf" class="smpl">obs-text</a> = &lt;obs-text, defined in [RFC7230], Section 3.2.6&gt;
    14501450<a href="#header.etag" class="smpl">opaque-tag</a> = DQUOTE *etagc DQUOTE
    14511451
     
    14821482      </div>
    14831483      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    1484       <p class="noprint"><a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a>
     1484      <p class="noprint"><a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a>
    14851485      </p>
    14861486      <div class="print2col">
     
    15341534               </ul>
    15351535            </li>
    1536             <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    1537                   <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.1</a>, <a href="#rfc.xref.Part1.3">1.2</a>, <a href="#rfc.xref.Part1.4">2.3.3</a>, <a href="#rfc.xref.Part1.5">8</a>, <a href="#rfc.xref.Part1.6">9</a>, <a href="#Part1"><b>10.1</b></a>, <a href="#rfc.xref.Part1.7">B</a>, <a href="#rfc.xref.Part1.8">B</a>, <a href="#rfc.xref.Part1.9">B</a>, <a href="#rfc.xref.Part1.10">C</a><ul>
    1538                         <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.10">C</a></li>
    1539                         <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.1</a></li>
    1540                         <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">B</a></li>
    1541                         <li><em>Section 3.2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">B</a></li>
    1542                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">2.3.3</a></li>
    1543                         <li><em>Section 7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.2</a></li>
    1544                         <li><em>Section 10</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">9</a></li>
    1545                      </ul>
    1546                   </li>
    1547                   <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1</a>, <a href="#rfc.xref.Part2.2">1</a>, <a href="#rfc.xref.Part2.3">2.3.3</a>, <a href="#rfc.xref.Part2.4">2.3.3</a>, <a href="#rfc.xref.Part2.5">3.2</a>, <a href="#rfc.xref.Part2.6">8</a>, <a href="#Part2"><b>10.1</b></a>, <a href="#rfc.xref.Part2.7">B</a><ul>
    1548                         <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">1</a></li>
    1549                         <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">2.3.3</a></li>
    1550                         <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.5">3.2</a></li>
    1551                         <li><em>Section 5.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4">2.3.3</a></li>
    1552                         <li><em>Section 7.1.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.7">B</a></li>
    1553                      </ul>
    1554                   </li>
    1555                   <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">3.5</a>, <a href="#rfc.xref.Part5.2">6</a>, <a href="#Part5"><b>10.1</b></a><ul>
    1556                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">3.5</a></li>
    1557                      </ul>
    1558                   </li>
    1559                   <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">1</a>, <a href="#rfc.xref.Part6.2">2.2.1</a>, <a href="#rfc.xref.Part6.3">2.3.1</a>, <a href="#rfc.xref.Part6.4">3.2</a>, <a href="#rfc.xref.Part6.5">3.3</a>, <a href="#rfc.xref.Part6.6">4.1</a>, <a href="#Part6"><b>10.1</b></a><ul>
    1560                         <li><em>Section 4.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.4">3.2</a>, <a href="#rfc.xref.Part6.5">3.3</a></li>
    1561                         <li><em>Section 4.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.6">4.1</a></li>
    1562                      </ul>
    1563                   </li>
    1564                </ul>
    1565             </li>
    15661536            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
    15671537                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>10.1</b></a></li>
     
    15761546                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#RFC5234"><b>10.1</b></a>, <a href="#rfc.xref.RFC5234.2">B</a><ul>
    15771547                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">B</a></li>
     1548                     </ul>
     1549                  </li>
     1550                  <li><em>RFC7230</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.1">1</a>, <a href="#rfc.xref.RFC7230.2">1.1</a>, <a href="#rfc.xref.RFC7230.3">1.2</a>, <a href="#rfc.xref.RFC7230.4">2.3.3</a>, <a href="#rfc.xref.RFC7230.5">8</a>, <a href="#rfc.xref.RFC7230.6">9</a>, <a href="#RFC7230"><b>10.1</b></a>, <a href="#rfc.xref.RFC7230.7">B</a>, <a href="#rfc.xref.RFC7230.8">B</a>, <a href="#rfc.xref.RFC7230.9">B</a>, <a href="#rfc.xref.RFC7230.10">C</a><ul>
     1551                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.10">C</a></li>
     1552                        <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.2">1.1</a></li>
     1553                        <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.8">B</a></li>
     1554                        <li><em>Section 3.2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.9">B</a></li>
     1555                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.4">2.3.3</a></li>
     1556                        <li><em>Section 7</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.3">1.2</a></li>
     1557                        <li><em>Section 10</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.6">9</a></li>
     1558                     </ul>
     1559                  </li>
     1560                  <li><em>RFC7231</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.1">1</a>, <a href="#rfc.xref.RFC7231.2">1</a>, <a href="#rfc.xref.RFC7231.3">2.3.3</a>, <a href="#rfc.xref.RFC7231.4">2.3.3</a>, <a href="#rfc.xref.RFC7231.5">3.2</a>, <a href="#rfc.xref.RFC7231.6">8</a>, <a href="#RFC7231"><b>10.1</b></a>, <a href="#rfc.xref.RFC7231.7">B</a><ul>
     1561                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.2">1</a></li>
     1562                        <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.3">2.3.3</a></li>
     1563                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.5">3.2</a></li>
     1564                        <li><em>Section 5.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.4">2.3.3</a></li>
     1565                        <li><em>Section 7.1.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.7">B</a></li>
     1566                     </ul>
     1567                  </li>
     1568                  <li><em>RFC7233</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.1">3.5</a>, <a href="#rfc.xref.RFC7233.2">6</a>, <a href="#RFC7233"><b>10.1</b></a><ul>
     1569                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7233.1">3.5</a></li>
     1570                     </ul>
     1571                  </li>
     1572                  <li><em>RFC7234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.1">1</a>, <a href="#rfc.xref.RFC7234.2">2.2.1</a>, <a href="#rfc.xref.RFC7234.3">2.3.1</a>, <a href="#rfc.xref.RFC7234.4">3.2</a>, <a href="#rfc.xref.RFC7234.5">3.3</a>, <a href="#rfc.xref.RFC7234.6">4.1</a>, <a href="#RFC7234"><b>10.1</b></a><ul>
     1573                        <li><em>Section 4.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.4">3.2</a>, <a href="#rfc.xref.RFC7234.5">3.3</a></li>
     1574                        <li><em>Section 4.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.6">4.1</a></li>
    15781575                     </ul>
    15791576                  </li>
Note: See TracChangeset for help on using the changeset viewer.