Changeset 1727 for draft-ietf-httpbis/latest/p4-conditional.html
- Timestamp:
- 05/07/12 17:06:19 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.html
r1725 r1727 992 992 they <em class="bcp14">MUST</em> forward the request towards the origin server. 993 993 </p> 994 <p id="rfc.section.3.1.p.6">If the request would, without the If-Match header field, result in anything other than a 2xx or 412 status code, then the 995 If-Match header field <em class="bcp14">MUST</em> be ignored. 994 <p id="rfc.section.3.1.p.6">If the request would, without the If-Match header field, result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx</a> or 412 status code, then the If-Match header field <em class="bcp14">MUST</em> be ignored. 996 995 </p> 997 996 <p id="rfc.section.3.1.p.7">Examples:</p> … … 1023 1022 <p id="rfc.section.3.2.p.5">If none of the entity-tags match, then the server <em class="bcp14">MAY</em> perform the requested method as if the If-None-Match header field did not exist, but <em class="bcp14">MUST</em> also ignore any If-Modified-Since header field(s) in the request. That is, if no entity-tags match, then the server <em class="bcp14">MUST NOT</em> return a <a href="#status.304" class="smpl">304 (Not Modified)</a> response. 1024 1023 </p> 1025 <p id="rfc.section.3.2.p.6">If the request would, without the If-None-Match header field, result in anything other than a 2xx or 304 status code, then 1026 the If-None-Match header field <em class="bcp14">MUST</em> be ignored. (See <a href="#rules.for.when.to.use.entity.tags.and.last-modified.dates" title="Rules for When to Use Entity-tags and Last-Modified Dates">Section 2.4</a> for a discussion of server behavior when both If-Modified-Since and If-None-Match appear in the same request.) 1024 <p id="rfc.section.3.2.p.6">If the request would, without the If-None-Match header field, result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx</a> or 304 status code, then the If-None-Match header field <em class="bcp14">MUST</em> be ignored. (See <a href="#rules.for.when.to.use.entity.tags.and.last-modified.dates" title="Rules for When to Use Entity-tags and Last-Modified Dates">Section 2.4</a> for a discussion of server behavior when both If-Modified-Since and If-None-Match appear in the same request.) 1027 1025 </p> 1028 1026 <p id="rfc.section.3.2.p.7">Examples:</p> … … 1090 1088 </pre><p id="rfc.section.3.4.p.3">An example of the field is:</p> 1091 1089 <div id="rfc.figure.u.16"></div><pre class="text"> If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT 1092 </pre><p id="rfc.section.3.4.p.5">If a request normally (i.e., in absence of the If-Unmodified-Since header field) would result in anything other than a 2xx 1093 or 412 status code, the If-Unmodified-Since header field <em class="bcp14">SHOULD</em> be ignored. 1090 </pre><p id="rfc.section.3.4.p.5">If a request normally (i.e., in absence of the If-Unmodified-Since header field) would result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx</a> or 412 status code, the If-Unmodified-Since header field <em class="bcp14">SHOULD</em> be ignored. 1094 1091 </p> 1095 1092 <p id="rfc.section.3.4.p.6">If the specified date is invalid, the header field <em class="bcp14">MUST</em> be ignored.
Note: See TracChangeset
for help on using the changeset viewer.