Changeset 1734 for draft-ietf-httpbis
- Timestamp:
- 06/07/12 13:59:02 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 10 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1727 r1734 449 449 } 450 450 @bottom-center { 451 content: "Expires January 6, 2013";451 content: "Expires January 7, 2013"; 452 452 } 453 453 @bottom-right { … … 491 491 <meta name="dct.creator" content="Reschke, J. F."> 492 492 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 493 <meta name="dct.issued" scheme="ISO8601" content="2012-07-0 5">493 <meta name="dct.issued" scheme="ISO8601" content="2012-07-06"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 523 523 </tr> 524 524 <tr> 525 <td class="left">Expires: January 6, 2013</td>525 <td class="left">Expires: January 7, 2013</td> 526 526 <td class="right">greenbytes</td> 527 527 </tr> 528 528 <tr> 529 529 <td class="left"></td> 530 <td class="right">July 5, 2012</td>530 <td class="right">July 6, 2012</td> 531 531 </tr> 532 532 </tbody> … … 561 561 in progress”. 562 562 </p> 563 <p>This Internet-Draft will expire on January 6, 2013.</p>563 <p>This Internet-Draft will expire on January 7, 2013.</p> 564 564 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 565 565 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1420 1420 <p id="rfc.section.3.3.2.p.1">When a message does not have a Transfer-Encoding header field and the payload body length can be determined prior to being 1421 1421 transferred, a Content-Length header field <em class="bcp14">SHOULD</em> be sent to indicate the length of the payload body that is either present as the message body, for requests and non-HEAD responses 1422 other than 304, or would have been present had the request been an unconditional GET. The length is expressed as a decimal 1423 number of octets. 1422 other than <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a>, or would have been present had the request been an unconditional GET. The length is expressed as a decimal number of octets. 1424 1423 </p> 1425 1424 <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.53"></span> <a href="#header.content-length" class="smpl">Content-Length</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a> … … 1446 1445 <ol> 1447 1446 <li> 1448 <p>Any response to a HEAD request and any response with a status code of 100-199, 204, or 304 is always terminated by the first 1449 empty line after the header fields, regardless of the header fields present in the message, and thus cannot contain a message 1450 body. 1447 <p>Any response to a HEAD request and any response with a status code of 100-199, 204, or <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> is always terminated by the first empty line after the header fields, regardless of the header fields present in the message, 1448 and thus cannot contain a message body. 1451 1449 </p> 1452 1450 </li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1727 r1734 1587 1587 Content-Length header field &SHOULD; be sent to indicate the length of the 1588 1588 payload body that is either present as the message body, for requests 1589 and non-HEAD responses other than 304, or would have been present had1590 the request been an unconditional GET. The length is expressed as a1591 decimal number of octets.1589 and non-HEAD responses other than <x:ref>304 (Not Modified)</x:ref>, or 1590 would have been present had the request been an unconditional GET. The 1591 length is expressed as a decimal number of octets. 1592 1592 </t> 1593 1593 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Length"/> … … 1644 1644 <x:lt><t> 1645 1645 Any response to a HEAD request and any response with a status 1646 code of 100-199, 204, or 304 is always terminated by the first 1647 empty line after the header fields, regardless of the header 1648 fields present in the message, and thus cannot contain a message body. 1646 code of 100-199, 204, or <x:ref>304 (Not Modified)</x:ref> is always 1647 terminated by the first empty line after the header fields, regardless of 1648 the header fields present in the message, and thus cannot contain a 1649 message body. 1649 1650 </t></x:lt> 1650 1651 <x:lt><t> -
draft-ietf-httpbis/latest/p2-semantics.html
r1732 r1734 2388 2388 </p> 2389 2389 <ol> 2390 <li>If the response status code is 200 or 203 and the request method was GET, the response payload is a representation of the2391 target resource.2392 </li> 2393 <li>If the response status code is 204, <a href="p5-range.html#status.206" class="smpl">206</a>, or 304and the request method was GET or HEAD, the response payload is a partial representation of the target resource.2390 <li>If the response status code is <a href="#status.200" class="smpl">200 (OK)</a> or <a href="#status.203" class="smpl">203 2391 (Non-Authoritative Information)</a> and the request method was GET, the response payload is a representation of the target resource. 2392 </li> 2393 <li>If the response status code is <a href="#status.204" class="smpl">204 (No Content)</a>, 206 (Partial Content, or <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> and the request method was GET or HEAD, the response payload is a partial representation of the target resource. 2394 2394 </li> 2395 2395 <li>If the response has a Content-Location header field, and that URI is the same as the effective request URI, the response payload -
draft-ietf-httpbis/latest/p2-semantics.xml
r1732 r1734 2704 2704 </t> 2705 2705 <t><list style="numbers"> 2706 <t>If the response status code is 200 or 203 and the request method was GET, 2706 <t>If the response status code is <x:ref>200 (OK)</x:ref> or <x:ref>203 2707 (Non-Authoritative Information)</x:ref> and the request method was GET, 2707 2708 the response payload is a representation of the target resource.</t> 2708 <t>If the response status code is 204, <x:ref>206</x:ref>, or 304 and the request method was GET 2709 or HEAD, the response payload is a partial representation of the target 2710 resource.</t> 2709 <t>If the response status code is <x:ref>204 (No Content)</x:ref>, 2710 <x:ref>206 (Partial Content</x:ref>, or <x:ref>304 (Not Modified)</x:ref> 2711 and the request method was GET or HEAD, the response payload is a partial 2712 representation of the target resource.</t> 2711 2713 <t>If the response has a Content-Location header field, and that URI is the same 2712 2714 as the effective request URI, the response payload is a representation of the -
draft-ietf-httpbis/latest/p4-conditional.html
r1733 r1734 991 991 they <em class="bcp14">MUST</em> forward the request towards the origin server. 992 992 </p> 993 <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 412status code, then the If-Match header field <em class="bcp14">MUST</em> be ignored.993 <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 (Successful)</a> or <a href="#status.412" class="smpl">412 (Precondition Failed)</a> status code, then the If-Match header field <em class="bcp14">MUST</em> be ignored. 994 994 </p> 995 995 <p id="rfc.section.3.1.p.7">Examples:</p> … … 1007 1007 updates of cached information with a minimum amount of transaction overhead. A client that has one or more representations 1008 1008 previously obtained from the target resource can send If-None-Match with a list of the associated entity-tags in the hope 1009 of receiving a 304response if at least one of those representations matches the selected representation.1009 of receiving a <a href="#status.304" class="smpl">304 (Not Modified)</a> response if at least one of those representations matches the selected representation. 1010 1010 </p> 1011 1011 <p id="rfc.section.3.2.p.2">If-None-Match can also be used with a value of "*" to prevent an unsafe request method (e.g., PUT) from inadvertently modifying … … 1021 1021 <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. 1022 1022 </p> 1023 <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 304status 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.)1023 <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 (Successful)</a> or <a href="#status.304" class="smpl">304 (Not Modified)</a> 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.) 1024 1024 </p> 1025 1025 <p id="rfc.section.3.2.p.7">Examples:</p> … … 1087 1087 </pre><p id="rfc.section.3.4.p.3">An example of the field is:</p> 1088 1088 <div id="rfc.figure.u.16"></div><pre class="text"> If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT 1089 </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 412status code, the If-Unmodified-Since header field <em class="bcp14">SHOULD</em> be ignored.1089 </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 (Successful)</a> or <a href="#status.412" class="smpl">412 (Precondition Failed)</a> status code, the If-Unmodified-Since header field <em class="bcp14">SHOULD</em> be ignored. 1090 1090 </p> 1091 1091 <p id="rfc.section.3.4.p.6">If the specified date is invalid, the header field <em class="bcp14">MUST</em> be ignored. -
draft-ietf-httpbis/latest/p4-conditional.xml
r1733 r1734 769 769 <t> 770 770 If the request would, without the If-Match header field, result in 771 anything other than a <x:ref>2xx </x:ref> or 412 status code, then the If-Match header field772 &MUST; be ignored.771 anything other than a <x:ref>2xx (Successful)</x:ref> or <x:ref>412 (Precondition Failed)</x:ref> 772 status code, then the If-Match header field &MUST; be ignored. 773 773 </t> 774 774 <t> … … 799 799 that has one or more representations previously obtained from the 800 800 target resource can send If-None-Match with a list of the associated 801 entity-tags in the hope of receiving a 304 response if at least one 802 of those representations matches the selected representation. 801 entity-tags in the hope of receiving a <x:ref>304 (Not Modified)</x:ref> 802 response if at least one of those representations matches the selected 803 representation. 803 804 </t> 804 805 <t> … … 834 835 <t> 835 836 If the request would, without the If-None-Match header field, result 836 in anything other than a <x:ref>2xx</x:ref> or 304 status code, then the If-None-Match 837 in anything other than a <x:ref>2xx (Successful)</x:ref> or 838 <x:ref>304 (Not Modified)</x:ref> status code, then the If-None-Match 837 839 header field &MUST; be ignored. (See <xref 838 840 target="rules.for.when.to.use.entity.tags.and.last-modified.dates"/> for … … 965 967 <t> 966 968 If a request normally (i.e., in absence of the If-Unmodified-Since 967 header field) would result in anything other than a <x:ref>2xx</x:ref> or 412 status code, 969 header field) would result in anything other than a <x:ref>2xx (Successful)</x:ref> 970 or <x:ref>412 (Precondition Failed)</x:ref> status code, 968 971 the If-Unmodified-Since header field &SHOULD; be ignored. 969 972 </t> … … 992 995 <iref primary="true" item="304 Not Modified (status code)" x:for-anchor=""/> 993 996 <iref primary="true" item="Status Codes" subitem="304 Not Modified" x:for-anchor=""/> 997 <x:anchor-alias value="304"/> 994 998 <x:anchor-alias value="304 (Not Modified)"/> 995 999 <t> … … 1196 1200 <x:source href="p2-semantics.xml" basename="p2-semantics"> 1197 1201 <x:defines>2xx</x:defines> 1202 <x:defines>2xx (Successful)</x:defines> 1198 1203 <x:defines>200 (OK)</x:defines> 1199 1204 </x:source> -
draft-ietf-httpbis/latest/p5-range.html
r1732 r1734 987 987 <li>The presence of a Range header field in a conditional GET (a request using one or both of If-Modified-Since and If-None-Match, 988 988 or one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition 989 is true. It does not affect the 304 (Not Modified)response returned if the conditional is false.989 is true. It does not affect the <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response returned if the conditional is false. 990 990 </li> 991 991 </ul> -
draft-ietf-httpbis/latest/p5-range.xml
r1732 r1734 840 840 one or both of If-Unmodified-Since and If-Match) modifies what 841 841 is returned if the GET is otherwise successful and the 842 condition is true. It does not affect the 304 (Not Modified)842 condition is true. It does not affect the <x:ref>304 (Not Modified)</x:ref> 843 843 response returned if the conditional is false.</t> 844 844 </list> … … 1044 1044 </front> 1045 1045 <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;"/> 1046 <x:source href="p4-conditional.xml" basename="p4-conditional"/> 1046 <x:source href="p4-conditional.xml" basename="p4-conditional"> 1047 <x:defines>304 (Not Modified)</x:defines> 1048 </x:source> 1047 1049 </reference> 1048 1050 -
draft-ietf-httpbis/latest/p6-cache.html
r1732 r1734 1099 1099 <h3 id="rfc.section.2.4.1"><a href="#rfc.section.2.4.1">2.4.1</a> <a id="freshening.responses" href="#freshening.responses">Freshening Responses with 304 Not Modified</a></h3> 1100 1100 <p id="rfc.section.2.4.1.p.1">When a cache receives a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response and already has one or more stored <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> responses for the same cache key, the cache needs to identify which of the stored responses are updated by this new response 1101 and then update the stored response(s) with the new information provided in the 304response.1101 and then update the stored response(s) with the new information provided in the <a href="p4-conditional.html#status.304" class="smpl">304</a> response. 1102 1102 </p> 1103 1103 <ul> … … 1119 1119 </li> 1120 1120 <li>retain any Warning header fields in the stored response with warn-code 2xx; and,</li> 1121 <li>use other header fields provided in the 304 response to replace all instances of the corresponding header fields in the stored 1122 response. 1121 <li>use other header fields provided in the <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response to replace all instances of the corresponding header fields in the stored response. 1123 1122 </li> 1124 1123 </ul> -
draft-ietf-httpbis/latest/p6-cache.xml
r1732 r1734 938 938 to identify which of the stored responses are updated by this new response 939 939 and then update the stored response(s) with the new information provided in 940 the 304response.940 the <x:ref>304</x:ref> response. 941 941 <list style="symbols"> 942 942 <t> … … 967 967 <t>retain any Warning header fields in the stored response with 968 968 warn-code 2xx; and,</t> 969 <t>use other header fields provided in the 304 response to replace970 all instances of the corresponding header fields in the stored971 response.</t>969 <t>use other header fields provided in the <x:ref>304 (Not Modified)</x:ref> 970 response to replace all instances of the corresponding header 971 fields in the stored response.</t> 972 972 </list> 973 973 </t> … … 2321 2321 <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;" /> 2322 2322 <x:source basename="p4-conditional" href="p4-conditional.xml"> 2323 <x:defines>304</x:defines> 2323 2324 <x:defines>304 (Not Modified)</x:defines> 2324 2325 </x:source>
Note: See TracChangeset
for help on using the changeset viewer.