Changeset 1779
- Timestamp:
- 14/07/12 18:33:38 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r1776 r1779 1259 1259 <div id="rfc.iref.n.1"></div> 1260 1260 <h4 id="rfc.section.7.2.1.1"><a href="#rfc.section.7.2.1.1">7.2.1.1</a> <a id="cache-request-directive.no-cache" href="#cache-request-directive.no-cache">no-cache</a></h4> 1261 <p id="rfc.section.7.2.1.1.p.1">The no-cacherequest directive indicates that a cache <em class="bcp14">MUST NOT</em> use a stored response to satisfy the request without successful validation on the origin server.1261 <p id="rfc.section.7.2.1.1.p.1">The "no-cache" request directive indicates that a cache <em class="bcp14">MUST NOT</em> use a stored response to satisfy the request without successful validation on the origin server. 1262 1262 </p> 1263 1263 <div id="rfc.iref.c.8"></div> 1264 1264 <div id="rfc.iref.n.2"></div> 1265 1265 <h4 id="rfc.section.7.2.1.2"><a href="#rfc.section.7.2.1.2">7.2.1.2</a> <a id="cache-request-directive.no-store" href="#cache-request-directive.no-store">no-store</a></h4> 1266 <p id="rfc.section.7.2.1.2.p.1">The no-storerequest directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either this request or any response to it. This directive applies to both private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.1266 <p id="rfc.section.7.2.1.2.p.1">The "no-store" request directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either this request or any response to it. This directive applies to both private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it. 1267 1267 </p> 1268 1268 <p id="rfc.section.7.2.1.2.p.2">This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches … … 1280 1280 </li> 1281 1281 </ul> 1282 <p id="rfc.section.7.2.1.3.p.2">The max-age request directive indicates that the client is unwilling to accept a response whose age is greater than the specified 1283 number of seconds. Unless the max-stale request directive is also present, the client is not willing to accept a stale response. 1282 <p id="rfc.section.7.2.1.3.p.2">The "max-age" request directive indicates that the client is unwilling to accept a response whose age is greater than the 1283 specified number of seconds. Unless the max-stale request directive is also present, the client is not willing to accept a 1284 stale response. 1284 1285 </p> 1285 1286 <p id="rfc.section.7.2.1.3.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form. … … 1293 1294 </li> 1294 1295 </ul> 1295 <p id="rfc.section.7.2.1.4.p.2">The max-stalerequest directive indicates that the client is willing to accept a response that has exceeded its expiration1296 <p id="rfc.section.7.2.1.4.p.2">The "max-stale" request directive indicates that the client is willing to accept a response that has exceeded its expiration 1296 1297 time. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its expiration time 1297 1298 by no more than the specified number of seconds. If no value is assigned to max-stale, then the client is willing to accept … … 1308 1309 </li> 1309 1310 </ul> 1310 <p id="rfc.section.7.2.1.5.p.2">The min-fresh request directive indicates that the client is willing to accept a response whose freshness lifetime is no less1311 than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh for1312 at least the specified number of seconds.1311 <p id="rfc.section.7.2.1.5.p.2">The "min-fresh" request directive indicates that the client is willing to accept a response whose freshness lifetime is no 1312 less than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh 1313 for at least the specified number of seconds. 1313 1314 </p> 1314 1315 <p id="rfc.section.7.2.1.5.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'min-fresh=20', not 'min-fresh="20"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form. … … 1317 1318 <div id="rfc.iref.n.3"></div> 1318 1319 <h4 id="rfc.section.7.2.1.6"><a href="#rfc.section.7.2.1.6">7.2.1.6</a> <a id="cache-request-directive.no-transform" href="#cache-request-directive.no-transform">no-transform</a></h4> 1319 <p id="rfc.section.7.2.1.6.p.1">The no-transformrequest directive indicates that an intermediary (whether or not it implements a cache) <em class="bcp14">MUST NOT</em> change the <a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a>, <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> or <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> request header fields, nor the request representation.1320 <p id="rfc.section.7.2.1.6.p.1">The "no-transform" request directive indicates that an intermediary (whether or not it implements a cache) <em class="bcp14">MUST NOT</em> change the <a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a>, <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> or <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> request header fields, nor the request representation. 1320 1321 </p> 1321 1322 <div id="rfc.iref.c.13"></div> 1322 1323 <div id="rfc.iref.o.1"></div> 1323 1324 <h4 id="rfc.section.7.2.1.7"><a href="#rfc.section.7.2.1.7">7.2.1.7</a> <a id="cache-request-directive.only-if-cached" href="#cache-request-directive.only-if-cached">only-if-cached</a></h4> 1324 <p id="rfc.section.7.2.1.7.p.1">The only-if-cachedrequest directive indicates that the client only wishes to obtain a stored response. If it receives this1325 <p id="rfc.section.7.2.1.7.p.1">The "only-if-cached" request directive indicates that the client only wishes to obtain a stored response. If it receives this 1325 1326 directive, a cache <em class="bcp14">SHOULD</em> either respond using a stored response that is consistent with the other constraints of the request, or respond with a <a href="p2-semantics.html#status.504" class="smpl">504 (Gateway 1326 1327 Timeout)</a> status code. If a group of caches is being operated as a unified system with good internal connectivity, a member cache <em class="bcp14">MAY</em> forward such a request within that group of caches. … … 1330 1331 <div id="rfc.iref.p.2"></div> 1331 1332 <h4 id="rfc.section.7.2.2.1"><a href="#rfc.section.7.2.2.1">7.2.2.1</a> <a id="cache-response-directive.only-if-cached" href="#cache-response-directive.only-if-cached">public</a></h4> 1332 <p id="rfc.section.7.2.2.1.p.1">The publicresponse directive indicates that a response whose associated request contains an 'Authentication' header <em class="bcp14">MAY</em> be stored (see <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section 3.2</a>).1333 <p id="rfc.section.7.2.2.1.p.1">The "public" response directive indicates that a response whose associated request contains an 'Authentication' header <em class="bcp14">MAY</em> be stored (see <a href="#caching.authenticated.responses" title="Storing Responses to Authenticated Requests">Section 3.2</a>). 1333 1334 </p> 1334 1335 <div id="rfc.iref.c.15"></div> … … 1340 1341 </li> 1341 1342 </ul> 1342 <p id="rfc.section.7.2.2.2.p.2">The privateresponse directive indicates that the response message is intended for a single user and <em class="bcp14">MUST NOT</em> be stored by a shared cache. A private cache <em class="bcp14">MAY</em> store the response.1343 <p id="rfc.section.7.2.2.2.p.2">The "private" response directive indicates that the response message is intended for a single user and <em class="bcp14">MUST NOT</em> be stored by a shared cache. A private cache <em class="bcp14">MAY</em> store the response. 1343 1344 </p> 1344 1345 <p id="rfc.section.7.2.2.2.p.3">If the private response directive specifies one or more field-names, this requirement is limited to the field-values associated … … 1362 1363 </li> 1363 1364 </ul> 1364 <p id="rfc.section.7.2.2.3.p.2">The no-cacheresponse directive indicates that the response <em class="bcp14">MUST NOT</em> be used to satisfy a subsequent request without successful validation on the origin server. This allows an origin server to1365 <p id="rfc.section.7.2.2.3.p.2">The "no-cache" response directive indicates that the response <em class="bcp14">MUST NOT</em> be used to satisfy a subsequent request without successful validation on the origin server. This allows an origin server to 1365 1366 prevent a cache from using it to satisfy a request without contacting it, even by caches that have been configured to return 1366 1367 stale responses. … … 1382 1383 <div id="rfc.iref.n.5"></div> 1383 1384 <h4 id="rfc.section.7.2.2.4"><a href="#rfc.section.7.2.2.4">7.2.2.4</a> <a id="cache-response-directive.no-store" href="#cache-response-directive.no-store">no-store</a></h4> 1384 <p id="rfc.section.7.2.2.4.p.1">The no-storeresponse directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either the immediate request or response. This directive applies to both private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.1385 <p id="rfc.section.7.2.2.4.p.1">The "no-store" response directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either the immediate request or response. This directive applies to both private and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it. 1385 1386 </p> 1386 1387 <p id="rfc.section.7.2.2.4.p.2">This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches … … 1390 1391 <div id="rfc.iref.m.4"></div> 1391 1392 <h4 id="rfc.section.7.2.2.5"><a href="#rfc.section.7.2.2.5">7.2.2.5</a> <a id="cache-response-directive.must-revalidate" href="#cache-response-directive.must-revalidate">must-revalidate</a></h4> 1392 <p id="rfc.section.7.2.2.5.p.1">The must-revalidateresponse directive indicates that once it has become stale, a cache <em class="bcp14">MUST NOT</em> use the response to satisfy subsequent requests without successful validation on the origin server.1393 <p id="rfc.section.7.2.2.5.p.1">The "must-revalidate" response directive indicates that once it has become stale, a cache <em class="bcp14">MUST NOT</em> use the response to satisfy subsequent requests without successful validation on the origin server. 1393 1394 </p> 1394 1395 <p id="rfc.section.7.2.2.5.p.2">The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances … … 1401 1402 <div id="rfc.iref.p.4"></div> 1402 1403 <h4 id="rfc.section.7.2.2.6"><a href="#rfc.section.7.2.2.6">7.2.2.6</a> <a id="cache-response-directive.proxy-revalidate" href="#cache-response-directive.proxy-revalidate">proxy-revalidate</a></h4> 1403 <p id="rfc.section.7.2.2.6.p.1">The proxy-revalidateresponse directive has the same meaning as the must-revalidate response directive, except that it does1404 <p id="rfc.section.7.2.2.6.p.1">The "proxy-revalidate" response directive has the same meaning as the must-revalidate response directive, except that it does 1404 1405 not apply to private caches. 1405 1406 </p> … … 1412 1413 </li> 1413 1414 </ul> 1414 <p id="rfc.section.7.2.2.7.p.2">The max-ageresponse directive indicates that the response is to be considered stale after its age is greater than the specified1415 <p id="rfc.section.7.2.2.7.p.2">The "max-age" response directive indicates that the response is to be considered stale after its age is greater than the specified 1415 1416 number of seconds. 1416 1417 </p> … … 1425 1426 </li> 1426 1427 </ul> 1427 <p id="rfc.section.7.2.2.8.p.2">The s-maxage response directive indicates that, in shared caches, the maximum age specified by this directive overrides the1428 maximum age specified by either the max-age directive or the <a href="#header.expires" class="smpl">Expires</a> header field. The s-maxage directive also implies the semantics of the proxy-revalidate response directive.1428 <p id="rfc.section.7.2.2.8.p.2">The "s-maxage" response directive indicates that, in shared caches, the maximum age specified by this directive overrides 1429 the maximum age specified by either the max-age directive or the <a href="#header.expires" class="smpl">Expires</a> header field. The s-maxage directive also implies the semantics of the proxy-revalidate response directive. 1429 1430 </p> 1430 1431 <p id="rfc.section.7.2.2.8.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 's-maxage=10', not 's-maxage="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form. … … 1433 1434 <div id="rfc.iref.n.6"></div> 1434 1435 <h4 id="rfc.section.7.2.2.9"><a href="#rfc.section.7.2.2.9">7.2.2.9</a> <a id="cache-response-directive.no-transform" href="#cache-response-directive.no-transform">no-transform</a></h4> 1435 <p id="rfc.section.7.2.2.9.p.1">The no-transformresponse directive indicates that an intermediary (regardless of whether it implements a cache) <em class="bcp14">MUST NOT</em> change the <a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a>, <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> or <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> response header fields, nor the response representation.1436 <p id="rfc.section.7.2.2.9.p.1">The "no-transform" response directive indicates that an intermediary (regardless of whether it implements a cache) <em class="bcp14">MUST NOT</em> change the <a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a>, <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> or <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> response header fields, nor the response representation. 1436 1437 </p> 1437 1438 <h3 id="rfc.section.7.2.3"><a href="#rfc.section.7.2.3">7.2.3</a> <a id="cache.control.extensions" href="#cache.control.extensions">Cache Control Extensions</a></h3> -
draft-ietf-httpbis/latest/p6-cache.xml
r1776 r1779 552 552 responses to be stored is present in the response. 553 553 </t> 554 555 554 <t> 556 555 In this specification, the following <x:ref>Cache-Control</x:ref> response … … 558 557 must-revalidate, public, s-maxage. 559 558 </t> 560 561 559 <t> 562 560 Note that cached responses that contain the "must-revalidate" and/or … … 1272 1270 </t> 1273 1271 1274 <section anchor="cache-request-directive" 1275 title="Request Cache-Control Directives"> 1272 <section title="Request Cache-Control Directives" anchor="cache-request-directive"> 1276 1273 1277 1274 <section title="no-cache" anchor="cache-request-directive.no-cache"> … … 1279 1276 <iref item="no-cache" primary="true" subitem="Cache Directive" /> 1280 1277 <t> 1281 The no-cacherequest directive indicates that a cache &MUST-NOT;1278 The "no-cache" request directive indicates that a cache &MUST-NOT; 1282 1279 use a stored response to satisfy the request without successful 1283 1280 validation on the origin server. … … 1289 1286 <iref item="no-store" primary="true" subitem="Cache Directive" /> 1290 1287 <t> 1291 The no-storerequest directive indicates that a cache &MUST-NOT;1288 The "no-store" request directive indicates that a cache &MUST-NOT; 1292 1289 store any part of either this request or any response to it. This 1293 1290 directive applies to both private and shared caches. "&MUST-NOT; … … 1322 1319 </t> 1323 1320 <t> 1324 The max-agerequest directive indicates that the client is unwilling to1321 The "max-age" request directive indicates that the client is unwilling to 1325 1322 accept a response whose age is greater than the specified number of 1326 1323 seconds. Unless the max-stale request directive is also present, the … … 1346 1343 </t> 1347 1344 <t> 1348 The max-stalerequest directive indicates that the client is willing1345 The "max-stale" request directive indicates that the client is willing 1349 1346 to accept a response that has exceeded its expiration time. If max-stale 1350 1347 is assigned a value, then the client is willing to accept a response … … 1372 1369 </t> 1373 1370 <t> 1374 The min-freshrequest directive indicates that the client is willing1371 The "min-fresh" request directive indicates that the client is willing 1375 1372 to accept a response whose freshness lifetime is no less than its 1376 1373 current age plus the specified time in seconds. That is, the client … … 1389 1386 <iref item="no-transform" primary="true" subitem="Cache Directive" /> 1390 1387 <t> 1391 The no-transformrequest directive indicates that an intermediary1388 The "no-transform" request directive indicates that an intermediary 1392 1389 (whether or not it implements a cache) &MUST-NOT; change the 1393 1390 <x:ref>Content-Encoding</x:ref>, <x:ref>Content-Range</x:ref> or … … 1401 1398 <iref item="only-if-cached" primary="true" subitem="Cache Directive" /> 1402 1399 <t> 1403 The only-if-cachedrequest directive indicates that the client only wishes1400 The "only-if-cached" request directive indicates that the client only wishes 1404 1401 to obtain a stored response. If it receives this directive, a cache &SHOULD; 1405 1402 either respond using a stored response that is consistent with the other … … 1420 1417 <iref item="public" primary="true" subitem="Cache Directive" /> 1421 1418 <t> 1422 The publicresponse directive indicates that a response whose1419 The "public" response directive indicates that a response whose 1423 1420 associated request contains an 'Authentication' header &MAY; be 1424 1421 stored (see <xref target="caching.authenticated.responses" />). … … 1438 1435 </t> 1439 1436 <t> 1440 The privateresponse directive indicates that the response message is1437 The "private" response directive indicates that the response message is 1441 1438 intended for a single user and &MUST-NOT; be stored by a shared cache. A 1442 1439 private cache &MAY; store the response. … … 1480 1477 </t> 1481 1478 <t> 1482 The no-cacheresponse directive indicates that the response &MUST-NOT;1479 The "no-cache" response directive indicates that the response &MUST-NOT; 1483 1480 be used to satisfy a subsequent request without successful validation on 1484 1481 the origin server. This allows an origin server to prevent a cache from … … 1518 1515 <iref item="no-store" primary="true" subitem="Cache Directive" /> 1519 1516 <t> 1520 The no-storeresponse directive indicates that a cache &MUST-NOT;1517 The "no-store" response directive indicates that a cache &MUST-NOT; 1521 1518 store any part of either the immediate request or response. This 1522 1519 directive applies to both private and shared caches. "&MUST-NOT; … … 1538 1535 <iref item="must-revalidate" primary="true" subitem="Cache Directive" /> 1539 1536 <t> 1540 The must-revalidateresponse directive indicates that once it has1537 The "must-revalidate" response directive indicates that once it has 1541 1538 become stale, a cache &MUST-NOT; use the response to satisfy subsequent 1542 1539 requests without successful validation on the origin server. … … 1561 1558 <iref item="proxy-revalidate" primary="true" subitem="Cache Directive" /> 1562 1559 <t> 1563 The proxy-revalidateresponse directive has the same meaning as the1560 The "proxy-revalidate" response directive has the same meaning as the 1564 1561 must-revalidate response directive, except that it does not apply to 1565 1562 private caches. … … 1579 1576 </t> 1580 1577 <t> 1581 The max-ageresponse directive indicates that the response is to be1578 The "max-age" response directive indicates that the response is to be 1582 1579 considered stale after its age is greater than the specified number of 1583 1580 seconds. … … 1602 1599 </t> 1603 1600 <t> 1604 The s-maxageresponse directive indicates that, in shared caches, the1601 The "s-maxage" response directive indicates that, in shared caches, the 1605 1602 maximum age specified by this directive overrides the maximum age 1606 1603 specified by either the max-age directive or the <x:ref>Expires</x:ref> … … 1619 1616 <iref item="no-transform" primary="true" subitem="Cache Directive" /> 1620 1617 <t> 1621 The no-transformresponse directive indicates that an intermediary1618 The "no-transform" response directive indicates that an intermediary 1622 1619 (regardless of whether it implements a cache) &MUST-NOT; change the 1623 1620 <x:ref>Content-Encoding</x:ref>, <x:ref>Content-Range</x:ref> or
Note: See TracChangeset
for help on using the changeset viewer.