Ignore:
Timestamp:
Feb 8, 2011, 5:14:45 PM (9 years ago)
Author:
fielding@…
Message:

update HTML

File:
1 edited

Legend:

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

    r1106 r1109  
    848848         value.
    849849      </p>
    850       <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.
     850      <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.
    851851      </p>
    852852      <div class="note" id="rfc.section.5.p.5">
     
    887887            assumptions about the validators they receive.
    888888         </li>
    889          <li>HTTP/1.0 clients and caches will ignore entity-tags. Generally, last-modified values received or used by these systems will
     889         <li>HTTP/1.0 clients and caches might ignore entity-tags. Generally, last-modified values received or used by these systems will
    890890            support transparent and efficient caching, and so HTTP/1.1 origin servers should provide Last-Modified values. In those rare
    891891            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
Note: See TracChangeset for help on using the changeset viewer.