Changeset 563 for draft-ietf-httpbis/latest/p4-conditional.html

Timestamp:

24/03/09 20:48:26 (13 years ago)

Author:

julian.reschke@…

Message:

replace <list> elements used for indentation by <x:note> elements

File:

• draft-ietf-httpbis/latest/p4-conditional.html (modified) (4 diffs)

draft-ietf-httpbis/latest/p4-conditional.html

@@ -29 +29 @@
 cite {
   font-style: normal;
+}
+div.note {
+  margin-left: 2em;
 }
 dd {
@@ -464 +467 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">March 12, 2009</td>
+            <td class="header right">March 24, 2009</td>
          </tr>
       </table>
@@ -792 +795 @@
          value.
       </p>
-      <p id="rfc.section.5.p.4">In order to be legal, a strong entity tag <em class="bcp14">MUST</em> change whenever the associated entity changes in any way. A weak entity tag <em class="bcp14">SHOULD</em> change whenever the associated entity changes in a semantically significant way. 
-      </p>
-      <dl class="empty">
-         <dd> <b>Note:</b> in order to provide semantically transparent caching, an origin server must avoid reusing a specific strong entity tag value
+      <p id="rfc.section.5.p.4">In order to be legal, a strong entity tag <em class="bcp14">MUST</em> change whenever the associated entity changes in any way. A weak entity tag <em class="bcp14">SHOULD</em> change whenever the associated entity changes in a semantically significant way.
+      </p>
+      <div class="note"> 
+         <p> <b>Note:</b> in order to provide semantically transparent caching, an origin server must avoid reusing a specific strong entity tag value
             for two different entities, or reusing a specific weak entity tag value for two semantically different entities. Cache entries
             might persist for arbitrarily long periods, regardless of expiration times, so it might be inappropriate to expect that a
             cache will never again attempt to validate an entry using a validator that it obtained at some point in the past.
-         </dd>
-      </dl>
-      <p id="rfc.section.5.p.5">HTTP/1.1 clients: </p>
+         </p> 
+      </div>
+      <p id="rfc.section.5.p.6">HTTP/1.1 clients: </p>
       <ul>
          <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).
@@ -812 +815 @@
          </li>
       </ul>
-      <p id="rfc.section.5.p.6">An HTTP/1.1 origin server, upon receiving a conditional request that includes both a Last-Modified date (e.g., in an If-Modified-Since
+      <p id="rfc.section.5.p.7">An HTTP/1.1 origin server, upon receiving a conditional request that includes both a Last-Modified date (e.g., in an If-Modified-Since
          or If-Unmodified-Since header field) and one or more entity tags (e.g., in an If-Match, If-None-Match, or If-Range header
          field) as cache validators, <em class="bcp14">MUST NOT</em> return a response status of 304 (Not Modified) unless doing so is consistent with all of the conditional header fields in
          the request.
       </p>
-      <p id="rfc.section.5.p.7">An HTTP/1.1 caching proxy, upon receiving a conditional request that includes both a Last-Modified date and one or more entity
+      <p id="rfc.section.5.p.8">An HTTP/1.1 caching proxy, upon receiving a conditional request that includes both a Last-Modified date and one or more entity
          tags as cache validators, <em class="bcp14">MUST NOT</em> return a locally cached response to the client unless that cached response is consistent with all of the conditional header
          fields in the request.