Changeset 157 for draft-ietf-httpbis/latest/p1-messaging.html
- Timestamp:
- 08/01/08 03:19:58 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r155 r157 768 768 <dl class="empty"> 769 769 <dd>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests. 770 The rules for determining the cacheability of HTTP responses are defined in <a href="p6-cache.html#caching" title=" Caching in HTTP">Section 2</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. Even if a resource is cacheable, there may be additional constraints on whether a cache can use the cached copy for a particular770 The rules for determining the cacheability of HTTP responses are defined in <a href="p6-cache.html#caching" title="Introduction">Section 1</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. Even if a resource is cacheable, there may be additional constraints on whether a cache can use the cached copy for a particular 771 771 request. 772 772 </dd> … … 825 825 <--------- response chain 826 826 </pre><p id="rfc.section.1.4.p.9">Not all responses are usefully cacheable, and some requests may contain modifiers which place special requirements on cache 827 behavior. HTTP requirements for cache behavior and cacheable responses are defined in <a href="p6-cache.html#caching" title=" Caching in HTTP">Section 2</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.827 behavior. HTTP requirements for cache behavior and cacheable responses are defined in <a href="p6-cache.html#caching" title="Introduction">Section 1</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. 828 828 </p> 829 829 <p id="rfc.section.1.4.p.10">In fact, there are a wide variety of architectures and configurations of caches and proxies currently being experimented with … … 1288 1288 to the entity being transferred. These header fields apply only to the message being transmitted. 1289 1289 </p> 1290 <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.60"></span> general-header = Cache-Control ; <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 3.2</a>1290 <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.60"></span> general-header = Cache-Control ; <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 15.2</a> 1291 1291 | Connection ; <a href="#header.connection" id="rfc.xref.header.connection.1" title="Connection">Section 8.1</a> 1292 1292 | Date ; <a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section 8.3</a> 1293 | Pragma ; <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 3.4</a>1293 | Pragma ; <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 15.4</a> 1294 1294 | Trailer ; <a href="#header.trailer" id="rfc.xref.header.trailer.2" title="Trailer">Section 8.6</a> 1295 1295 | Transfer-Encoding ; <a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.4" title="Transfer-Encoding">Section 8.7</a> 1296 1296 | Upgrade ; <a href="#header.upgrade" id="rfc.xref.header.upgrade.1" title="Upgrade">Section 8.8</a> 1297 1297 | Via ; <a href="#header.via" id="rfc.xref.header.via.1" title="Via">Section 8.9</a> 1298 | Warning ; <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.warning" title="Warning">Section 3.6</a>1298 | Warning ; <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.warning" title="Warning">Section 15.6</a> 1299 1299 </pre><p id="rfc.section.4.5.p.3">General-header field names can be extended reliably only in combination with a change in the protocol version. However, new 1300 1300 or experimental header fields may be given the semantics of general header fields if all parties in the communication recognize … … 2649 2649 <li class="indline1"><em>Part5</em> <a class="iref" href="#Part5"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part5.1">D.3</a></li> 2650 2650 <li class="indline1"><em>Part6</em> <a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a>, <a class="iref" href="#rfc.xref.Part6.3">4.5</a>, <a class="iref" href="#rfc.xref.Part6.4">4.5</a>, <a class="iref" href="#rfc.xref.Part6.5">4.5</a>, <a class="iref" href="#Part6"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part6.6">D.3</a><ul class="ind"> 2651 <li class="indline1"><em>Section 2</em> <a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a></li>2652 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part6.3">4.5</a></li>2653 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.Part6.4">4.5</a></li>2654 <li class="indline1"><em>Section 3.6</em> <a class="iref" href="#rfc.xref.Part6.5">4.5</a></li>2651 <li class="indline1"><em>Section 1</em> <a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a></li> 2652 <li class="indline1"><em>Section 15.2</em> <a class="iref" href="#rfc.xref.Part6.3">4.5</a></li> 2653 <li class="indline1"><em>Section 15.4</em> <a class="iref" href="#rfc.xref.Part6.4">4.5</a></li> 2654 <li class="indline1"><em>Section 15.6</em> <a class="iref" href="#rfc.xref.Part6.5">4.5</a></li> 2655 2655 </ul> 2656 2656 </li>
Note: See TracChangeset
for help on using the changeset viewer.