Changeset 1691 for draft-ietf-httpbis/latest/p4-conditional.xml
- Timestamp:
- Jun 23, 2012, 4:27:41 AM (7 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.xml
r1689 r1691 301 301 received. However, if a resource has distinct representations that differ 302 302 only in their metadata, such as might occur with content negotiation over 303 media types that happen to share the same data format, then a server304 &SHOULD; incorporate additional information in the validator to303 media types that happen to share the same data format, then the origin 304 server &SHOULD; incorporate additional information in the validator to 305 305 distinguish those representations and avoid confusing cache behavior. 306 306 </t> … … 312 312 representations of the resource, or due to a desire by the resource owner 313 313 to group representations by some self-determined set of equivalency 314 rather than unique sequences of data. A weak entity-tag &SHOULD; change315 w henever the origin serverconsiders prior representations to be316 unacceptable as a substitute for the current representation. In other 317 words, a weak entity-tag &SHOULD; change whenever the origin server wants318 caches toinvalidate old responses.314 rather than unique sequences of data. An origin server &SHOULD; change a 315 weak entity-tag whenever it considers prior representations to be 316 unacceptable as a substitute for the current representation. In other words, 317 a weak entity-tag ought to change whenever the origin server wants caches to 318 invalidate old responses. 319 319 </t> 320 320 <t> … … 715 715 last-modified values received or used by these systems will 716 716 support transparent and efficient caching, and so HTTP/1.1 origin 717 servers s houldprovide Last-Modified values. In those rare cases717 servers still ought to provide Last-Modified values. In those rare cases 718 718 where the use of a Last-Modified value as a validator by an 719 719 HTTP/1.0 system could result in a serious problem, then HTTP/1.1 … … 735 735 <x:anchor-alias value="If-Match"/> 736 736 <t> 737 The "If-Match" header field &MAY;be used to make a request method737 The "If-Match" header field can be used to make a request method 738 738 conditional on the current existence or value of an entity-tag for 739 739 one or more representations of the target resource. If-Match is … … 787 787 <x:anchor-alias value="If-None-Match"/> 788 788 <t> 789 The "If-None-Match" header field &MAY;be used to make a request method789 The "If-None-Match" header field can be used to make a request method 790 790 conditional on not matching any of the current entity-tag values for 791 791 representations of the target resource. If-None-Match is primarily … … 798 798 </t> 799 799 <t> 800 If-None-Match &MAY;also be used with a value of "*" to prevent an unsafe800 If-None-Match can also be used with a value of "*" to prevent an unsafe 801 801 request method (e.g., PUT) from inadvertently modifying an existing 802 802 representation of the target resource when the client believes that … … 857 857 <x:anchor-alias value="If-Modified-Since"/> 858 858 <t> 859 The "If-Modified-Since" header field &MAY;be used to make a request859 The "If-Modified-Since" header field can be used to make a request 860 860 method conditional by modification date: if the selected representation 861 861 has not been modified since the time specified in this field, then … … 940 940 <x:anchor-alias value="If-Unmodified-Since"/> 941 941 <t> 942 The "If-Unmodified-Since" header field &MAY;be used to make a request942 The "If-Unmodified-Since" header field can be used to make a request 943 943 method conditional by modification date: if the selected representation 944 944 has been modified since the time specified in this field, then the … … 959 959 </artwork></figure> 960 960 <t> 961 If the request normally (i.e., withoutthe If-Unmodified-Since961 If a request normally (i.e., in absence of the If-Unmodified-Since 962 962 header field) would result in anything other than a 2xx or 412 status code, 963 963 the If-Unmodified-Since header field &SHOULD; be ignored.
Note: See TracChangeset
for help on using the changeset viewer.