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

Timestamp:

09/02/11 01:14:45 (9 years ago)

Author:

fielding@…

Message:

update HTML

File:

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

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

@@ -848 +848 @@
          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 representation changes in any way. A weak entity-tag <em class="bcp14">SHOULD</em> change whenever the associated representation changes in a semantically significant way.
+      <p id="rfc.section.5.p.4">In order to be legitimate, a strong entity-tag <em class="bcp14">MUST</em> change whenever the associated representation changes in any way. A weak entity-tag <em class="bcp14">SHOULD</em> change whenever the associated representation changes in a semantically significant way.
       </p>
       <div class="note" id="rfc.section.5.p.5"> 
@@ -887 +887 @@
             assumptions about the validators they receive.
          </li>
-         <li>HTTP/1.0 clients and caches will ignore entity-tags. Generally, last-modified values received or used by these systems will
+         <li>HTTP/1.0 clients and caches might ignore entity-tags. Generally, last-modified values received or used by these systems will
             support transparent and efficient caching, and so HTTP/1.1 origin servers should provide Last-Modified values. In those rare
             cases where the use of a Last-Modified value as a validator by an HTTP/1.0 system could result in a serious problem, then