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.xml

    r754 r755  
    620620   HTTP/1.1 clients:
    621621  <list style="symbols">
    622      <t>If an entity tag has been provided by the origin server, &MUST;
    623         use that entity tag in any cache-conditional request (using If-Match
    624         or If-None-Match).</t>
    625 
    626      <t>If only a Last-Modified value has been provided by the origin
    627         server, &SHOULD; use that value in non-subrange cache-conditional
    628         requests (using If-Modified-Since).</t>
    629 
    630      <t>If only a Last-Modified value has been provided by an HTTP/1.0
    631         origin server, &MAY; use that value in subrange cache-conditional
    632         requests (using If-Unmodified-Since:). The user agent &SHOULD;
     622     <t>&MUST; use that entity tag in any cache-conditional request (using
     623        If-Match or If-None-Match) if an entity tag has been provided by the
     624        origin server.</t>
     625
     626     <t>&SHOULD; use the Last-Modified value in non-subrange cache-conditional
     627        requests (using If-Modified-Since) if only a Last-Modified value has
     628        been provided by the origin server. </t>
     629
     630     <t>&MAY; use the Last-Modified value in subrange cache-conditional
     631        requests (using If-Unmodified-Since) if only a Last-Modified value has
     632        been provided by an HTTP/1.0 origin server. The user agent &SHOULD;
    633633        provide a way to disable this, in case of difficulty.</t>
    634634
    635      <t>If both an entity tag and a Last-Modified value have been
    636         provided by the origin server, &SHOULD; use both validators in
    637         cache-conditional requests. This allows both HTTP/1.0 and
    638         HTTP/1.1 caches to respond appropriately.</t>
     635     <t>&SHOULD; use both validators in cache-conditional requests if both an
     636        entity tag and a Last-Modified value have been provided by the origin
     637        server. This allows both HTTP/1.0 and HTTP/1.1 caches to respond
     638        appropriately.</t>
    639639  </list>
    640640</t>
Note: See TracChangeset for help on using the changeset viewer.