Changeset 1111
- Timestamp:
- 10/02/11 02:24:03 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1106 r1111 353 353 } 354 354 @bottom-center { 355 content: "Expires August 1 2, 2011";355 content: "Expires August 14, 2011"; 356 356 } 357 357 @bottom-right { … … 403 403 <meta name="dct.creator" content="Reschke, J. F."> 404 404 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 405 <meta name="dct.issued" scheme="ISO8601" content="2011-02- 08">405 <meta name="dct.issued" scheme="ISO8601" content="2011-02-10"> 406 406 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 407 407 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: August 1 2, 2011</td>436 <td class="left">Expires: August 14, 2011</td> 437 437 <td class="right">HP</td> 438 438 </tr> … … 487 487 <tr> 488 488 <td class="left"></td> 489 <td class="right">February 8, 2011</td>489 <td class="right">February 10, 2011</td> 490 490 </tr> 491 491 </tbody> … … 514 514 in progress”. 515 515 </p> 516 <p>This Internet-Draft will expire on August 1 2, 2011.</p>516 <p>This Internet-Draft will expire on August 14, 2011.</p> 517 517 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 518 518 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1099 1099 and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases. 1100 1100 </p> 1101 <p id="rfc.section.7.6.p.4">If the request passes through a cache that has one or more stored responses for the effective request URI, those stored responses <em class="bcp14">SHOULD</em> be marked as stale if the response to the PUT request has a success status code. Responses to the PUT method are not cacheable. 1101 <p id="rfc.section.7.6.p.4">Responses to the PUT method are not cacheable. If a PUT request passes through a cache that has one or more stored responses 1102 for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 2.5</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). 1102 1103 </p> 1103 1104 <p id="rfc.section.7.6.p.5">The fundamental difference between the POST and PUT requests is reflected in the different meaning of the effective request … … 1126 1127 enacted, or 204 (No Content) if the action has been enacted but the response does not include a representation. 1127 1128 </p> 1128 <p id="rfc.section.7.7.p.3"> If the request passes through a cache and the effective request URI identifies one or more currently cached representations,1129 those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to the DELETE method are not cacheable.1129 <p id="rfc.section.7.7.p.3">Responses to the DELETE method are not cacheable. If a DELETE request passes through a cache that has one or more stored responses 1130 for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 2.5</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). 1130 1131 </p> 1131 1132 <h2 id="rfc.section.7.8"><a href="#rfc.section.7.8">7.8</a> <a id="TRACE" href="#TRACE">TRACE</a></h2> … … 1225 1226 <dd>a representation containing the request message as received by the end server.</dd> 1226 1227 </dl> 1227 <p id="rfc.section.8.2.1.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.1 1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses.1228 <p id="rfc.section.8.2.1.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.13"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses. 1228 1229 </p> 1229 1230 <div id="rfc.iref.28"></div> … … 1259 1260 when the response would otherwise be 200 (OK). 1260 1261 </p> 1261 <p id="rfc.section.8.2.4.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.1 2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 203 responses.1262 <p id="rfc.section.8.2.4.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.14"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 203 responses. 1262 1263 </p> 1263 1264 <div id="rfc.iref.31"></div> … … 1290 1291 defined in <a href="p5-range.html#status.206" title="206 Partial Content">Section 3.1</a> of <a href="#Part5" id="rfc.xref.Part5.11"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. 1291 1292 </p> 1292 <p id="rfc.section.8.2.7.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.1 3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 206 responses.1293 <p id="rfc.section.8.2.7.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.15"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 206 responses. 1293 1294 </p> 1294 1295 <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a> <a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2> … … 1314 1315 <p id="rfc.section.8.3.1.p.3">If the server has a preferred choice of representation, it <em class="bcp14">SHOULD</em> include the specific URI for that representation in the Location field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection. 1315 1316 </p> 1316 <p id="rfc.section.8.3.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.1 4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 300 responses.1317 <p id="rfc.section.8.3.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.16"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 300 responses. 1317 1318 </p> 1318 1319 <div id="rfc.iref.35"></div> … … 1322 1323 request URI to one or more of the new references returned by the server, where possible. 1323 1324 </p> 1324 <p id="rfc.section.8.3.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.1 5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 301 responses.1325 <p id="rfc.section.8.3.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.17"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 301 responses. 1325 1326 </p> 1326 1327 <p id="rfc.section.8.3.2.p.3">The new permanent URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the representation of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s). … … 1494 1495 — that is left to the discretion of the server owner. 1495 1496 </p> 1496 <p id="rfc.section.8.4.11.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.1 6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses.1497 <p id="rfc.section.8.4.11.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.18"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses. 1497 1498 </p> 1498 1499 <div id="rfc.iref.53"></div> … … 2710 2711 </li> 2711 2712 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/240">http://tools.ietf.org/wg/httpbis/trac/ticket/240</a>>: "Migrate Upgrade details from RFC2817" 2713 </li> 2714 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/225">http://tools.ietf.org/wg/httpbis/trac/ticket/225</a>>: "PUT side effect: invalidation or just stale?" 2712 2715 </li> 2713 2716 </ul> … … 2925 2928 </ul> 2926 2929 </li> 2927 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">1.2.2</a>, <a href="#rfc.xref.Part6.2">1.2.2</a>, <a href="#rfc.xref.Part6.3">2.1.1</a>, <a href="#rfc.xref.Part6.4">4.1.1</a>, <a href="#rfc.xref.Part6.5">5</a>, <a href="#rfc.xref.Part6.6">5</a>, <a href="#rfc.xref.Part6.7">6.1</a>, <a href="#rfc.xref.Part6.8">7.3</a>, <a href="#rfc.xref.Part6.9">7.4</a>, <a href="#rfc.xref.Part6.10">7.5</a>, <a href="#rfc.xref.Part6.11"> 8.2.1</a>, <a href="#rfc.xref.Part6.12">8.2.4</a>, <a href="#rfc.xref.Part6.13">8.2.7</a>, <a href="#rfc.xref.Part6.14">8.3.1</a>, <a href="#rfc.xref.Part6.15">8.3.2</a>, <a href="#rfc.xref.Part6.16">8.4.11</a>, <a href="#Part6"><b>13.1</b></a><ul>2930 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">1.2.2</a>, <a href="#rfc.xref.Part6.2">1.2.2</a>, <a href="#rfc.xref.Part6.3">2.1.1</a>, <a href="#rfc.xref.Part6.4">4.1.1</a>, <a href="#rfc.xref.Part6.5">5</a>, <a href="#rfc.xref.Part6.6">5</a>, <a href="#rfc.xref.Part6.7">6.1</a>, <a href="#rfc.xref.Part6.8">7.3</a>, <a href="#rfc.xref.Part6.9">7.4</a>, <a href="#rfc.xref.Part6.10">7.5</a>, <a href="#rfc.xref.Part6.11">7.6</a>, <a href="#rfc.xref.Part6.12">7.7</a>, <a href="#rfc.xref.Part6.13">8.2.1</a>, <a href="#rfc.xref.Part6.14">8.2.4</a>, <a href="#rfc.xref.Part6.15">8.2.7</a>, <a href="#rfc.xref.Part6.16">8.3.1</a>, <a href="#rfc.xref.Part6.17">8.3.2</a>, <a href="#rfc.xref.Part6.18">8.4.11</a>, <a href="#Part6"><b>13.1</b></a><ul> 2928 2931 <li><em>Section 2.3.1</em> <a href="#rfc.xref.Part6.10">7.5</a></li> 2929 <li><em>Section 2.3.1.1</em> <a href="#rfc.xref.Part6.11">8.2.1</a>, <a href="#rfc.xref.Part6.12">8.2.4</a>, <a href="#rfc.xref.Part6.13">8.2.7</a>, <a href="#rfc.xref.Part6.14">8.3.1</a>, <a href="#rfc.xref.Part6.15">8.3.2</a>, <a href="#rfc.xref.Part6.16">8.4.11</a></li> 2932 <li><em>Section 2.3.1.1</em> <a href="#rfc.xref.Part6.13">8.2.1</a>, <a href="#rfc.xref.Part6.14">8.2.4</a>, <a href="#rfc.xref.Part6.15">8.2.7</a>, <a href="#rfc.xref.Part6.16">8.3.1</a>, <a href="#rfc.xref.Part6.17">8.3.2</a>, <a href="#rfc.xref.Part6.18">8.4.11</a></li> 2933 <li><em>Section 2.5</em> <a href="#rfc.xref.Part6.11">7.6</a>, <a href="#rfc.xref.Part6.12">7.7</a></li> 2930 2934 <li><em>Section 2.8</em> <a href="#rfc.xref.Part6.7">6.1</a></li> 2931 2935 <li><em>Section 3.1</em> <a href="#rfc.xref.Part6.1">1.2.2</a>, <a href="#rfc.xref.Part6.5">5</a></li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1106 r1111 77 77 <!ENTITY p7-status-codes "<xref target='Part7' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 78 78 <!ENTITY p6-heuristic "<xref target='Part6' x:rel='#heuristic.freshness' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 79 <!ENTITY p6-explicit "<xref target='Part6' x:rel='#calculating.freshness.lifetime' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 79 <!ENTITY p6-explicit "<xref target='Part6' x:rel='#calculating.freshness.lifetime' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 80 <!ENTITY p6-invalid "<xref target='Part6' x:rel='#invalidation.after.updates.or.deletions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 80 81 ]> 81 82 <?rfc toc="yes" ?> … … 1042 1043 </t> 1043 1044 <t> 1044 If the request passes through a cache that has one or more stored 1045 responses for the effective request URI, those stored responses 1046 &SHOULD; be marked as stale if the response to the PUT request 1047 has a success status code. Responses to the PUT method are 1048 not cacheable. 1045 Responses to the PUT method are not cacheable. If a PUT request passes 1046 through a cache that has one or more stored responses for the effective 1047 request URI, those stored responses will be invalidated (see 1048 &p6-invalid;). 1049 1049 </t> 1050 1050 <t> … … 1102 1102 </t> 1103 1103 <t> 1104 If the request passes through a cache and the effective request URI 1105 identifies one or more currently cached representations, those entries &SHOULD; be 1106 treated as stale. Responses to the DELETE method are not cacheable. 1104 Responses to the DELETE method are not cacheable. If a DELETE request 1105 passes through a cache that has one or more stored responses for the 1106 effective request URI, those stored responses will be invalidated (see 1107 &p6-invalid;). 1107 1108 </t> 1108 1109 </section> … … 4050 4051 "Migrate Upgrade details from RFC2817" 4051 4052 </t> 4053 <t> 4054 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/225"/>: 4055 "PUT side effect: invalidation or just stale?" 4056 </t> 4057 4052 4058 </list> 4053 4059 </t>
Note: See TracChangeset
for help on using the changeset viewer.