Changeset 994 for draft-ietf-httpbis/latest/p4-conditional.xml
- Timestamp:
- 07/09/10 11:46:12 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.xml
r981 r994 231 231 A future draft will reorganize the sections to better reflect the content. 232 232 In particular, the sections on resource metadata will be discussed first 233 and then followed by each conditional request-header , concluding with a233 and then followed by each conditional request-header field, concluding with a 234 234 definition of precedence and the expectation of ordering strong validator 235 235 checks before weak validator checks. It is likely that more content from … … 573 573 <list style="symbols"> 574 574 <t>The validator is about to be used by a client in an If-Modified-Since 575 or If-Unmodified-Since header , because the client575 or If-Unmodified-Since header field, because the client 576 576 has a cache entry for the associated representation, and</t> 577 577 <t>That cache entry includes a Date value, which gives the time … … 640 640 unless the risk of a breakdown in semantic transparency that 641 641 could result from using this date in an If-Modified-Since header 642 would lead to serious problems.</t>642 field would lead to serious problems.</t> 643 643 </list> 644 644 </t> … … 764 764 appropriate cache validation mechanism, and the specification of any 765 765 validator comparison function more complex than byte-equality would 766 open up a can of worms. Thus, comparisons of any other header s766 open up a can of worms. Thus, comparisons of any other header fields 767 767 (except Last-Modified, for compatibility with HTTP/1.0) are never 768 768 used for purposes of validating a cache entry. … … 795 795 If any of the entity-tags match the entity-tag of the representation that 796 796 would have been returned in the response to a similar GET request 797 (without the If-Match header ) on that resource, or if "*" is given797 (without the If-Match header field) on that resource, or if "*" is given 798 798 and any current representation exists for that resource, then the server &MAY; 799 799 perform the requested method as if the If-Match header field did not … … 810 810 <t> 811 811 If the request would, without the If-Match header field, result in 812 anything other than a 2xx or 412 status code, then the If-Match header 812 anything other than a 2xx or 412 status code, then the If-Match header field 813 813 &MUST; be ignored. 814 814 </t> … … 864 864 </artwork></figure> 865 865 <t> 866 A GET method with an If-Modified-Since header and no Range header867 requests that the representation be transferred only if it has868 been modified since the date given by the If-Modified-Since header .866 A GET method with an If-Modified-Since header field and no Range header 867 field requests that the representation be transferred only if it has 868 been modified since the date given by the If-Modified-Since header field. 869 869 The algorithm for determining this includes the following cases: 870 870 <list style="numbers"> … … 902 902 </t><t> 903 903 <x:h>Note:</x:h> If a client uses an arbitrary date in the If-Modified-Since 904 header instead of a date taken from the Last-Modified headerfor904 header field instead of a date taken from the Last-Modified header field for 905 905 the same request, the client needs to be aware that this 906 906 date is interpreted in the server's understanding of time. … … 954 954 If any of the entity-tags match the entity-tag of the representation that 955 955 would have been returned in the response to a similar GET request 956 (without the If-None-Match header ) on that resource, or if "*" is956 (without the If-None-Match header field) on that resource, or if "*" is 957 957 given and any current representation exists for that resource, then the 958 958 server &MUST-NOT; perform the requested method, unless required to do … … 975 975 If the request would, without the If-None-Match header field, result 976 976 in anything other than a 2xx or 304 status code, then the If-None-Match 977 header &MUST; be ignored. (See <xref target="rules.for.when.to.use.entity.tags.and.last-modified.dates"/> for a discussion of977 header field &MUST; be ignored. (See <xref target="rules.for.when.to.use.entity.tags.and.last-modified.dates"/> for a discussion of 978 978 server behavior when both If-Modified-Since and If-None-Match appear 979 979 in the same request.) … … 1014 1014 in a 200 response to a GET request on the same resource has not been modified 1015 1015 since the time specified in this field, the server &SHOULD; perform the 1016 requested operation as if the If-Unmodified-Since header were not1016 requested operation as if the If-Unmodified-Since header field were not 1017 1017 present. 1018 1018 </t> … … 1035 1035 <t> 1036 1036 If the request normally (i.e., without the If-Unmodified-Since 1037 header ) would result in anything other than a 2xx or 412 status code,1038 the If-Unmodified-Since header &SHOULD; be ignored.1039 </t> 1040 <t> 1041 If the specified date is invalid, the header is ignored.1037 header field) would result in anything other than a 2xx or 412 status code, 1038 the If-Unmodified-Since header field &SHOULD; be ignored. 1039 </t> 1040 <t> 1041 If the specified date is invalid, the header field is ignored. 1042 1042 </t> 1043 1043 <t> … … 1585 1585 </t> 1586 1586 <t> 1587 Ongoing work on IANA Message Header Registration (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/40"/>):1587 Ongoing work on IANA Message Header Field Registration (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/40"/>): 1588 1588 <list style="symbols"> 1589 1589 <t> 1590 Reference RFC 3984, and update header registrations for headers defined1590 Reference RFC 3984, and update header field registrations for header fields defined 1591 1591 in this document. 1592 1592 </t> … … 1628 1628 <t> 1629 1629 Rewrite ABNFs to spell out whitespace rules, factor out 1630 header value format definitions.1630 header field value format definitions. 1631 1631 </t> 1632 1632 </list>
Note: See TracChangeset
for help on using the changeset viewer.