Ignore:
Timestamp:
15/09/13 23:42:16 (7 years ago)
Author:
fielding@…
Message:

okay, usable for use cases is kind of lame, but so is defining what use means; addresses #495

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

Legend:

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

    r2402 r2403  
    446446  }
    447447  @bottom-center {
    448        content: "Expires March 18, 2014";
     448       content: "Expires March 19, 2014";
    449449  }
    450450  @bottom-right {
     
    489489      <meta name="dct.creator" content="Reschke, J. F.">
    490490      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    491       <meta name="dct.issued" scheme="ISO8601" content="2013-09-14">
     491      <meta name="dct.issued" scheme="ISO8601" content="2013-09-15">
    492492      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    493493      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an 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.">
     
    515515            </tr>
    516516            <tr>
    517                <td class="left">Expires: March 18, 2014</td>
    518                <td class="right">September 14, 2013</td>
     517               <td class="left">Expires: March 19, 2014</td>
     518               <td class="right">September 15, 2013</td>
    519519            </tr>
    520520         </tbody>
     
    543543         in progress”.
    544544      </p>
    545       <p>This Internet-Draft will expire on March 18, 2014.</p>
     545      <p>This Internet-Draft will expire on March 19, 2014.</p>
    546546      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    547547      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    704704         metadata, such as when two different media types are available for the same representation data.
    705705      </p>
    706       <p id="rfc.section.2.1.p.9">A "use" of a validator occurs when either a client generates a request and includes the validator in a precondition or when
    707          a server compares two validators. Weak validators are only usable for use cases that do not depend on exact equality of the
    708          representation data, such as cache validation, or for limiting the scope of web traversals to recently changed representations.
    709          Strong validators are usable and preferred for all conditional requests, including cache validation, partial content ranges,
    710          and "lost update" avoidance.
     706      <p id="rfc.section.2.1.p.9">Strong validators are usable for all conditional requests, including cache validation, partial content ranges, and "lost update"
     707         avoidance. Weak validators are only usable when the client does not require exact equality with previously obtained representation
     708         data, such as when validating a cache entry or limiting a web traversal to recent changes.
    711709      </p>
    712710      <div id="rfc.iref.l.1"></div>
     
    923921      <p id="rfc.section.2.4.p.4">A client: </p>
    924922      <ul>
    925          <li><em class="bcp14">MUST</em> send that entity-tag in any cache-conditional request (using <a href="#header.if-match" class="smpl">If-Match</a> or <a href="#header.if-none-match" class="smpl">If-None-Match</a>) if an entity-tag has been provided by the origin server.
    926          </li>
    927          <li><em class="bcp14">SHOULD</em> send the <a href="#header.last-modified" class="smpl">Last-Modified</a> value in non-subrange cache-conditional requests (using <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a>) if only a Last-Modified value has been provided by the origin server.
    928          </li>
    929          <li><em class="bcp14">MAY</em> send the <a href="#header.last-modified" class="smpl">Last-Modified</a> value in subrange cache-conditional requests (using <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a>) if only a Last-Modified value has been provided by an HTTP/1.0 origin server. The user agent <em class="bcp14">SHOULD</em> provide a way to disable this, in case of difficulty.
    930          </li>
    931          <li><em class="bcp14">SHOULD</em> send both validators in cache-conditional requests if both an entity-tag and a <a href="#header.last-modified" class="smpl">Last-Modified</a> value have been provided by the origin server. This allows both HTTP/1.0 and HTTP/1.1 caches to respond appropriately.
     923         <li><em class="bcp14">MUST</em> send that entity-tag in any cache validation request (using <a href="#header.if-match" class="smpl">If-Match</a> or <a href="#header.if-none-match" class="smpl">If-None-Match</a>) if an entity-tag has been provided by the origin server.
     924         </li>
     925         <li><em class="bcp14">SHOULD</em> send the <a href="#header.last-modified" class="smpl">Last-Modified</a> value in non-subrange cache validation requests (using <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a>) if only a Last-Modified value has been provided by the origin server.
     926         </li>
     927         <li><em class="bcp14">MAY</em> send the <a href="#header.last-modified" class="smpl">Last-Modified</a> value in subrange cache validation requests (using <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a>) if only a Last-Modified value has been provided by an HTTP/1.0 origin server. The user agent <em class="bcp14">SHOULD</em> provide a way to disable this, in case of difficulty.
     928         </li>
     929         <li><em class="bcp14">SHOULD</em> send both validators in cache validation requests if both an entity-tag and a <a href="#header.last-modified" class="smpl">Last-Modified</a> value have been provided by the origin server. This allows both HTTP/1.0 and HTTP/1.1 caches to respond appropriately.
    932930         </li>
    933931      </ul>
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r2402 r2403  
    284284</t>
    285285<t>
    286    A "use" of a validator occurs when either a client generates a request
    287    and includes the validator in a precondition or when a server
    288    compares two validators.
    289    Weak validators are only usable for use cases that do not depend on exact
    290    equality of the representation data, such as cache validation, or for
    291    limiting the scope of web traversals to recently changed representations.
    292    Strong validators are usable and preferred for all conditional requests,
    293    including cache validation, partial content ranges, and "lost update"
    294    avoidance.
     286   Strong validators are usable for all conditional requests, including cache
     287   validation, partial content ranges, and "lost update" avoidance.
     288   Weak validators are only usable when the client does not require exact
     289   equality with previously obtained representation data, such as when
     290   validating a cache entry or limiting a web traversal to recent changes.
    295291</t>
    296292</section>
     
    629625   A client:
    630626  <list style="symbols">
    631      <t>&MUST; send that entity-tag in any cache-conditional request (using
     627     <t>&MUST; send that entity-tag in any cache validation request (using
    632628        <x:ref>If-Match</x:ref> or <x:ref>If-None-Match</x:ref>) if an
    633629        entity-tag has been provided by the origin server.</t>
    634630
    635631     <t>&SHOULD; send the <x:ref>Last-Modified</x:ref> value in non-subrange
    636         cache-conditional requests (using <x:ref>If-Modified-Since</x:ref>)
     632        cache validation requests (using <x:ref>If-Modified-Since</x:ref>)
    637633        if only a Last-Modified value has been provided by the origin server.</t>
    638634
    639635     <t>&MAY; send the <x:ref>Last-Modified</x:ref> value in subrange
    640         cache-conditional requests (using <x:ref>If-Unmodified-Since</x:ref>)
     636        cache validation requests (using <x:ref>If-Unmodified-Since</x:ref>)
    641637        if only a Last-Modified value has been provided by an HTTP/1.0 origin
    642638        server. The user agent &SHOULD; provide a way to disable this, in case
    643639        of difficulty.</t>
    644640
    645      <t>&SHOULD; send both validators in cache-conditional requests if both an
     641     <t>&SHOULD; send both validators in cache validation requests if both an
    646642        entity-tag and a <x:ref>Last-Modified</x:ref> value have been provided
    647643        by the origin server. This allows both HTTP/1.0 and HTTP/1.1 caches to
Note: See TracChangeset for help on using the changeset viewer.