Changeset 2390
- Timestamp:
- 14/09/13 05:30:06 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.html
r2389 r2390 704 704 </p> 705 705 <p id="rfc.section.2.1.p.9">A "use" of a validator occurs when either a client generates a request and includes the validator in a precondition or when 706 a server compares two validators. Weak validators are only usable in contexts that do not depend on exact equality of the 707 representation data. Strong validators are usable and preferred for all conditional requests, including cache validation, 708 partial content ranges, and "lost update" avoidance. 706 a server compares two validators. Weak validators are only usable for use cases that do not depend on exact equality of the 707 representation data, such as cache validation, or for limiting the scope of web traversals to recently changed representations. 708 Strong validators are usable and preferred for all conditional requests, including cache validation, partial content ranges, 709 and "lost update" avoidance. 709 710 </p> 710 711 <div id="rfc.iref.l.1"></div> … … 941 942 the target resource that has an entity-tag matching a member of the list of entity-tags provided in the field-value. 942 943 </p> 943 <p id="rfc.section.3.1.p.2">A recipient <em class="bcp14">MUST</em> use the strong comparison function when comparing entity-tags for If-Match (<a href="#entity.tag.comparison" title="Comparison">Section 2.3.2</a>). 944 <p id="rfc.section.3.1.p.2">A recipient <em class="bcp14">MUST</em> use the strong comparison function when comparing entity-tags for If-Match (<a href="#entity.tag.comparison" title="Comparison">Section 2.3.2</a>), since the client intends this precondition to prevent the method from being applied if there have been any changes to the 945 representation data. 944 946 </p> 945 947 <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.7"></span> <a href="#header.if-match" class="smpl">If-Match</a> = "*" / 1#<a href="#header.etag" class="smpl">entity-tag</a> … … 968 970 target resource that has an entity-tag matching a member of the list of entity-tags provided in the field-value. 969 971 </p> 970 <p id="rfc.section.3.2.p.2">A recipient <em class="bcp14">MUST</em> use the weak comparison function when comparing entity-tags for If-None-Match (<a href="#entity.tag.comparison" title="Comparison">Section 2.3.2</a>) .972 <p id="rfc.section.3.2.p.2">A recipient <em class="bcp14">MUST</em> use the weak comparison function when comparing entity-tags for If-None-Match (<a href="#entity.tag.comparison" title="Comparison">Section 2.3.2</a>), since weak entity-tags can be used for cache validation even if there have been changes to the representation data. 971 973 </p> 972 974 <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.8"></span> <a href="#header.if-none-match" class="smpl">If-None-Match</a> = "*" / 1#<a href="#header.etag" class="smpl">entity-tag</a> -
draft-ietf-httpbis/latest/p4-conditional.xml
r2389 r2390 287 287 and includes the validator in a precondition or when a server 288 288 compares two validators. 289 Weak validators are only usable in contexts that do not depend on exact 290 equality of the representation data. 289 Weak validators are only usable for use cases that do not depend on exact 290 equality of the representation data, such as cache validation, or for 291 limiting the scope of web traversals to recently changed representations. 291 292 Strong validators are usable and preferred for all conditional requests, 292 293 including cache validation, partial content ranges, and "lost update" … … 677 678 <t> 678 679 A recipient &MUST; use the strong comparison function when comparing 679 entity-tags for If-Match (<xref target="entity.tag.comparison"/>). 680 entity-tags for If-Match (<xref target="entity.tag.comparison"/>), since 681 the client intends this precondition to prevent the method from being 682 applied if there have been any changes to the representation data. 680 683 </t> 681 684 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Match"/> … … 736 739 <t> 737 740 A recipient &MUST; use the weak comparison function when comparing 738 entity-tags for If-None-Match (<xref target="entity.tag.comparison"/>). 741 entity-tags for If-None-Match (<xref target="entity.tag.comparison"/>), 742 since weak entity-tags can be used for cache validation even if there have 743 been changes to the representation data. 739 744 </t> 740 745 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-None-Match"/>
Note: See TracChangeset
for help on using the changeset viewer.