Changeset 1109 for draft-ietf-httpbis/latest/p4-conditional.html
- Timestamp:
- 09/02/11 01:14:45 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.html
r1106 r1109 848 848 value. 849 849 </p> 850 <p id="rfc.section.5.p.4">In order to be leg al, 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. 851 851 </p> 852 852 <div class="note" id="rfc.section.5.p.5"> … … 887 887 assumptions about the validators they receive. 888 888 </li> 889 <li>HTTP/1.0 clients and caches willignore entity-tags. Generally, last-modified values received or used by these systems will889 <li>HTTP/1.0 clients and caches might ignore entity-tags. Generally, last-modified values received or used by these systems will 890 890 support transparent and efficient caching, and so HTTP/1.1 origin servers should provide Last-Modified values. In those rare 891 891 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.