Ignore:
Timestamp:
Feb 1, 2010, 6:42:42 AM (10 years ago)
Author:
julian.reschke@…
Message:

editorial: improve list style / sentence ordering in client requirements

File:
1 edited

Legend:

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

    r754 r755  
    827827      <p id="rfc.section.5.p.6">HTTP/1.1 clients: </p>
    828828      <ul>
    829          <li>If an entity tag has been provided by the origin server, <em class="bcp14">MUST</em> use that entity tag in any cache-conditional request (using If-Match or If-None-Match).
    830          </li>
    831          <li>If only a Last-Modified value has been provided by the origin server, <em class="bcp14">SHOULD</em> use that value in non-subrange cache-conditional requests (using If-Modified-Since).
    832          </li>
    833          <li>If only a Last-Modified value has been provided by an HTTP/1.0 origin server, <em class="bcp14">MAY</em> use that value in subrange cache-conditional requests (using If-Unmodified-Since:). The user agent <em class="bcp14">SHOULD</em> provide a way to disable this, in case of difficulty.
    834          </li>
    835          <li>If both an entity tag and a Last-Modified value have been provided by the origin server, <em class="bcp14">SHOULD</em> use both validators in cache-conditional requests. This allows both HTTP/1.0 and HTTP/1.1 caches to respond appropriately.
     829         <li><em class="bcp14">MUST</em> use that entity tag in any cache-conditional request (using If-Match or If-None-Match) if an entity tag has been provided
     830            by the origin server.
     831         </li>
     832         <li><em class="bcp14">SHOULD</em> use the Last-Modified value in non-subrange cache-conditional requests (using If-Modified-Since) if only a Last-Modified value
     833            has been provided by the origin server.
     834         </li>
     835         <li><em class="bcp14">MAY</em> use the Last-Modified value in subrange cache-conditional requests (using If-Unmodified-Since) if only a Last-Modified value
     836            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.
     837         </li>
     838         <li><em class="bcp14">SHOULD</em> use both validators in cache-conditional requests if both an entity tag and a Last-Modified value have been provided by the
     839            origin server. This allows both HTTP/1.0 and HTTP/1.1 caches to respond appropriately.
    836840         </li>
    837841      </ul>
Note: See TracChangeset for help on using the changeset viewer.