* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #307: 307.diff

File 307.diff, 25.5 KB (added by julian.reschke@gmx.de, 3 years ago)

Proposed patch (work in progress)

  • p6-cache.xml

     
    11841184      x:for-anchor="" /> 
    11851185   <x:anchor-alias value="Cache-Control"/> 
    11861186   <x:anchor-alias value="cache-directive"/> 
    1187    <x:anchor-alias value="cache-extension"/> 
    1188    <x:anchor-alias value="cache-request-directive"/> 
    1189    <x:anchor-alias value="cache-response-directive"/> 
    11901187<t> 
    11911188   The "Cache-Control" header field is used to specify directives for 
    11921189   caches along the request/response chain. Such cache directives are 
     
    12131210   to all recipients along the request/response chain. It is not possible to  
    12141211   target a directive to a specific cache. 
    12151212</t> 
    1216 <t>Cache directives are identified by a token, to be compared case-insensitively, and have an optional argument.</t> 
    1217 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Cache-Control"/><iref primary="true" item="Grammar" subitem="cache-extension"/> 
     1213<t> 
     1214   Cache directives are identified by a token, to be compared case-insensitively, 
     1215   and have an optional argument, that can use both token and quoted-string 
     1216   syntax. Recipients &MUST; accept both forms.  
     1217</t> 
     1218<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Cache-Control"/><iref primary="true" item="Grammar" subitem="cache-directive"/> 
    12181219  <x:ref>Cache-Control</x:ref>   = 1#<x:ref>cache-directive</x:ref> 
    12191220 
    1220   <x:ref>cache-directive</x:ref> = <x:ref>cache-request-directive</x:ref> 
    1221      / <x:ref>cache-response-directive</x:ref> 
    1222  
    1223   <x:ref>cache-extension</x:ref> = <x:ref>token</x:ref> [ "=" ( <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref> ) ] 
     1221  <x:ref>cache-directive</x:ref> = <x:ref>token</x:ref> [ "=" ( <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref> ) ] 
    12241222</artwork></figure> 
     1223<t> 
     1224   For the cache directives defined below, no argument is defined (nor allowed) 
     1225   otherwise stated otherwise. 
     1226</t> 
    12251227 
    12261228<section anchor="cache-request-directive"  
    12271229   title="Request Cache-Control Directives"> 
    1228    <x:anchor-alias value="cache-request-directive" /> 
    12291230 
    1230 <figure><artwork type="abnf2616"><iref item="Grammar" primary="true"  
    1231    subitem="cache-request-directive" /> 
    1232   <x:ref>cache-request-directive</x:ref> = 
    1233        "no-cache" 
    1234      / "no-store" 
    1235      / "max-age" "=" <x:ref>delta-seconds</x:ref> 
    1236      / "max-stale" [ "=" <x:ref>delta-seconds</x:ref> ] 
    1237      / "min-fresh" "=" <x:ref>delta-seconds</x:ref> 
    1238      / "no-transform" 
    1239      / "only-if-cached" 
    1240      / <x:ref>cache-extension</x:ref> 
    1241 </artwork></figure> 
    1242  
    1243 <t> 
    1244    <x:dfn>no-cache</x:dfn> 
     1231<section title="no-cache" anchor="cache-request-directive.no-cache"> 
    12451232   <iref item="Cache Directives" primary="true" subitem="no-cache" /> 
    12461233   <iref item="no-cache" primary="true" subitem="Cache Directive" /> 
    1247    <list> 
    1248       <t>The no-cache request directive indicates that a cache &MUST-NOT;  
    1249       use a stored response to satisfy the request without successful  
    1250       validation on the origin server.</t>  
    1251    </list> 
     1234<t> 
     1235   The no-cache request directive indicates that a cache &MUST-NOT;  
     1236   use a stored response to satisfy the request without successful  
     1237   validation on the origin server. 
    12521238</t> 
    1253 <t> 
    1254    <x:dfn>no-store</x:dfn> 
     1239</section> 
     1240  
     1241<section title="no-store" anchor="cache-request-directive.no-store"> 
    12551242   <iref item="Cache Directives" primary="true" subitem="no-store" /> 
    12561243   <iref item="no-store" primary="true" subitem="Cache Directive" /> 
    1257    <list> 
    1258       <t>The no-store request directive indicates that a cache &MUST-NOT; 
    1259       store any part of either this request or any response to it. This 
    1260       directive applies to both private and shared caches. "&MUST-NOT; 
    1261       store" in this context means that the cache &MUST-NOT; intentionally 
    1262       store the information in non-volatile storage, and &MUST; make a 
    1263       best-effort attempt to remove the information from volatile storage as 
    1264       promptly as possible after forwarding it.</t> 
    1265       <t>This directive is NOT a reliable or sufficient mechanism for ensuring 
    1266       privacy. In particular, malicious or compromised caches might not 
    1267       recognize or obey this directive, and communications networks might be 
    1268       vulnerable to eavesdropping.</t> 
    1269       <t>Note that if a request containing this directive is satisfied from a 
    1270       cache, the no-store request directive does not apply to the already 
    1271       stored response.</t> 
    1272    </list> 
     1244<t> 
     1245   The no-store request directive indicates that a cache &MUST-NOT; 
     1246   store any part of either this request or any response to it. This 
     1247   directive applies to both private and shared caches. "&MUST-NOT; 
     1248   store" in this context means that the cache &MUST-NOT; intentionally 
     1249   store the information in non-volatile storage, and &MUST; make a 
     1250   best-effort attempt to remove the information from volatile storage as 
     1251   promptly as possible after forwarding it. 
    12731252</t> 
    12741253<t> 
    1275    <x:dfn>max-age</x:dfn> 
     1254   This directive is NOT a reliable or sufficient mechanism for ensuring 
     1255   privacy. In particular, malicious or compromised caches might not 
     1256   recognize or obey this directive, and communications networks might be 
     1257   vulnerable to eavesdropping. 
     1258</t> 
     1259<t> 
     1260   Note that if a request containing this directive is satisfied from a 
     1261   cache, the no-store request directive does not apply to the already 
     1262   stored response. 
     1263</t> 
     1264</section> 
     1265 
     1266<section title="max-age" anchor="cache-request-directive.max-age"> 
    12761267   <iref item="Cache Directives" primary="true" subitem="max-age" /> 
    12771268   <iref item="max-age" primary="true" subitem="Cache Directive" /> 
     1269<t> 
     1270   Argument syntax: 
    12781271   <list> 
    1279       <t>The max-age request directive indicates that the client is unwilling to 
    1280       accept a response whose age is greater than the specified number of 
    1281       seconds. Unless the max-stale request directive is also present, the 
    1282       client is not willing to accept a stale response.</t> 
     1272      <t> 
     1273        <x:ref>delta-seconds</x:ref> (see <xref target="delta-seconds"/>) 
     1274      </t> 
    12831275   </list> 
    12841276</t> 
    12851277<t> 
    1286    <x:dfn>max-stale</x:dfn> 
     1278   The max-age request directive indicates that the client is unwilling to 
     1279   accept a response whose age is greater than the specified number of 
     1280   seconds. Unless the max-stale request directive is also present, the 
     1281   client is not willing to accept a stale response. 
     1282</t> 
     1283</section> 
     1284 
     1285<section title="max-stale" anchor="cache-request-directive.max-stale"> 
    12871286   <iref item="Cache Directives" primary="true" subitem="max-stale" /> 
    12881287   <iref item="max-stale" primary="true" subitem="Cache Directive" /> 
     1288<t> 
     1289   Argument syntax: 
    12891290   <list> 
    1290       <t>The max-stale request directive indicates that the client is willing 
    1291       to accept a response that has exceeded its expiration time. If max-stale 
    1292       is assigned a value, then the client is willing to accept a response 
    1293       that has exceeded its expiration time by no more than the specified 
    1294       number of seconds. If no value is assigned to max-stale, then the client 
    1295       is willing to accept a stale response of any age.</t> 
     1291      <t> 
     1292        <x:ref>delta-seconds</x:ref> (see <xref target="delta-seconds"/>) 
     1293      </t> 
    12961294   </list> 
    12971295</t> 
    12981296<t> 
    1299    <x:dfn>min-fresh</x:dfn> 
     1297   The max-stale request directive indicates that the client is willing 
     1298   to accept a response that has exceeded its expiration time. If max-stale 
     1299   is assigned a value, then the client is willing to accept a response 
     1300   that has exceeded its expiration time by no more than the specified 
     1301   number of seconds. If no value is assigned to max-stale, then the client 
     1302   is willing to accept a stale response of any age. 
     1303</t> 
     1304</section> 
     1305 
     1306<section title="min-fresh" anchor="cache-request-directive.min-fresh"> 
    13001307   <iref item="Cache Directives" primary="true" subitem="min-fresh" /> 
    13011308   <iref item="min-fresh" primary="true" subitem="Cache Directive" /> 
     1309<t> 
     1310   Argument syntax: 
    13021311   <list> 
    1303       <t>The min-fresh request directive indicates that the client is willing 
    1304       to accept a response whose freshness lifetime is no less than its 
    1305       current age plus the specified time in seconds. That is, the client 
    1306       wants a response that will still be fresh for at least the specified 
    1307       number of seconds.</t> 
     1312      <t> 
     1313        <x:ref>delta-seconds</x:ref> (see <xref target="delta-seconds"/>) 
     1314      </t> 
    13081315   </list> 
    13091316</t> 
    13101317<t> 
    1311    <x:dfn>no-transform</x:dfn> 
     1318   The min-fresh request directive indicates that the client is willing 
     1319   to accept a response whose freshness lifetime is no less than its 
     1320   current age plus the specified time in seconds. That is, the client 
     1321   wants a response that will still be fresh for at least the specified 
     1322   number of seconds. 
     1323</t> 
     1324</section> 
     1325 
     1326<section title="no-transform" anchor="cache-request-directive.no-transform"> 
    13121327   <iref item="Cache Directives" primary="true" subitem="no-transform" /> 
    13131328   <iref item="no-transform" primary="true" subitem="Cache Directive" /> 
    1314    <list> 
    1315       <t>The no-transform request directive indicates that an intermediary 
    1316         (whether or not it implements a cache) &MUST-NOT; change the  
    1317         Content-Encoding, Content-Range or Content-Type request header fields,  
    1318         nor the request representation.</t> 
    1319    </list> 
     1329<t> 
     1330   The no-transform request directive indicates that an intermediary 
     1331   (whether or not it implements a cache) &MUST-NOT; change the  
     1332   Content-Encoding, Content-Range or Content-Type request header fields,  
     1333   nor the request representation. 
    13201334</t> 
    1321 <t> 
    1322    <x:dfn>only-if-cached</x:dfn> 
     1335</section> 
     1336 
     1337<section title="only-if-cached" anchor="cache-request-directive.only-if-cached"> 
    13231338   <iref item="Cache Directives" primary="true" subitem="only-if-cached" /> 
    13241339   <iref item="only-if-cached" primary="true" subitem="Cache Directive" /> 
    1325    <list> 
    1326       <t>The only-if-cached request directive indicates that the client only 
    1327       wishes to obtain a stored response. If it receives this directive, a 
    1328       cache &SHOULD; either respond using a stored response that is consistent 
    1329       with the other constraints of the request, or respond with a 504 
    1330       (Gateway Timeout) status code. If a group of caches is being operated as 
    1331       a unified system with good internal connectivity, a member cache &MAY; 
    1332       forward such a request within that group of caches.</t> 
    1333    </list> 
     1340<t> 
     1341   The only-if-cached request directive indicates that the client only 
     1342   wishes to obtain a stored response. If it receives this directive, a 
     1343   cache &SHOULD; either respond using a stored response that is consistent 
     1344   with the other constraints of the request, or respond with a 504 
     1345   (Gateway Timeout) status code. If a group of caches is being operated as 
     1346   a unified system with good internal connectivity, a member cache &MAY; 
     1347   forward such a request within that group of caches. 
    13341348</t> 
    13351349</section> 
     1350</section> 
    13361351 
    13371352<section anchor="cache-response-directive"  
    13381353   title="Response Cache-Control Directives"> 
    13391354   <x:anchor-alias value="cache-response-directive" /> 
    13401355 
    1341 <figure><artwork type="abnf2616"><iref item="Grammar" primary="true"  
     1356<!--<figure><artwork type="abnf2616"><iref item="Grammar" primary="true"  
    13421357   subitem="cache-response-directive" /> 
    13431358  <x:ref>cache-response-directive</x:ref> = 
    13441359       "public" 
     
    13511366     / "max-age" "=" <x:ref>delta-seconds</x:ref> 
    13521367     / "s-maxage" "=" <x:ref>delta-seconds</x:ref> 
    13531368     / <x:ref>cache-extension</x:ref> 
    1354 </artwork></figure> 
     1369</artwork></figure>--> 
    13551370 
    1356 <t> 
    1357    <x:dfn>public</x:dfn> 
     1371<section title="public" anchor="cache-response-directive.only-if-cached"> 
    13581372   <iref item="Cache Directives" primary="true" subitem="public" /> 
    13591373   <iref item="public" primary="true" subitem="Cache Directive" /> 
    1360    <list> 
    1361       <t>The public response directive indicates that a response whose  
    1362         associated request contains an 'Authentication' header &MAY; be  
    1363         stored (see <xref target="caching.authenticated.responses" />).</t> 
    1364   </list> 
     1374<t> 
     1375   The public response directive indicates that a response whose  
     1376   associated request contains an 'Authentication' header &MAY; be  
     1377   stored (see <xref target="caching.authenticated.responses" />). 
    13651378</t> 
    1366 <t> 
    1367    <x:dfn>private</x:dfn> 
     1379</section> 
     1380 
     1381<section title="private" anchor="cache-response-directive.private"> 
    13681382   <iref item="Cache Directives" primary="true" subitem="private" /> 
    13691383   <iref item="private" primary="true" subitem="Cache Directive" /> 
     1384<t> 
     1385   Argument syntax: 
    13701386   <list> 
    1371       <t>The private response directive indicates that the response message is 
    1372       intended for a single user and &MUST-NOT; be stored by a shared cache. A 
    1373       private cache &MAY; store the response.</t> 
    1374       <t>If the private response directive specifies one or more field-names, 
    1375       this requirement is limited to the field-values associated with the 
    1376       listed response header fields. That is, a shared cache &MUST-NOT; store 
    1377       the specified field-names(s), whereas it &MAY; store the remainder of the 
    1378       response message.</t> 
    1379       <t>The field-names given are not limited to the set of standard header 
    1380       fields defined by this specification. Field names are case-insensitive. 
     1387      <t> 
     1388        #<x:ref>field-name</x:ref> 
    13811389      </t> 
    1382       <t> <x:h>Note:</x:h> This usage of the word "private" only controls 
    1383       where the response can be stored; it cannot ensure the privacy of the 
    1384       message content. Also, private response directives with field-names are 
    1385       often handled by implementations as if an unqualified private directive 
    1386       was received; i.e., the special handling for the qualified form is not 
    1387       widely implemented.</t> 
    13881390   </list> 
    13891391</t> 
    13901392<t> 
    1391    <x:dfn>no-cache</x:dfn> 
     1393   The private response directive indicates that the response message is 
     1394   intended for a single user and &MUST-NOT; be stored by a shared cache. A 
     1395   private cache &MAY; store the response. 
     1396</t> 
     1397<t> 
     1398   If the private response directive specifies one or more field-names, 
     1399   this requirement is limited to the field-values associated with the 
     1400   listed response header fields. That is, a shared cache &MUST-NOT; store 
     1401   the specified field-names(s), whereas it &MAY; store the remainder of the 
     1402   response message. 
     1403</t> 
     1404<t> 
     1405   The field-names given are not limited to the set of standard header 
     1406   fields defined by this specification. Field names are case-insensitive. 
     1407</t> 
     1408<t> 
     1409   <x:h>Note:</x:h> This usage of the word "private" only controls 
     1410   where the response can be stored; it cannot ensure the privacy of the 
     1411   message content. Also, private response directives with field-names are 
     1412   often handled by implementations as if an unqualified private directive 
     1413   was received; i.e., the special handling for the qualified form is not 
     1414   widely implemented. 
     1415</t> 
     1416<t> 
     1417   <x:h>Note:</x:h> For compatibility with non-robust recipients, even a 
     1418   single-entry list of field names &SHOULD; be sent using the quoted-string 
     1419   syntax. 
     1420</t> 
     1421</section> 
     1422 
     1423<section title="no-cache" anchor="cache-response-directive.no-cache"> 
    13921424   <iref item="Cache Directives" primary="true" subitem="no-cache" /> 
    13931425   <iref item="no-cache" primary="true" subitem="Cache Directive" /> 
     1426<t> 
     1427   Argument syntax: 
    13941428   <list> 
    1395       <t>The no-cache response directive indicates that the response &MUST-NOT; 
    1396       be used to satisfy a subsequent request without successful validation on 
    1397       the origin server. This allows an origin server to prevent a cache from 
    1398       using it to satisfy a request without contacting it, even by caches that 
    1399       have been configured to return stale responses.</t> 
    1400       <t>If the no-cache response directive specifies one or more field-names, 
    1401       then a cache MAY use the response to satisfy a subsequent request, 
    1402       subject to any other restrictions on caching. However, any header fields 
    1403       in the response that have the field-name(s) listed &MUST-NOT; be sent 
    1404       in the response to a subsequent request without successful revalidation 
    1405       with the origin server. This allows an origin server to prevent the 
    1406       re-use of certain header fields in a response, while still allowing 
    1407       caching of the rest of the response.</t>  
    1408       <t>The field-names given are not limited to the set of standard header 
    1409       fields defined by this specification. Field names are case-insensitive. 
     1429      <t> 
     1430        #<x:ref>field-name</x:ref> 
    14101431      </t> 
    1411       <t> <x:h>Note:</x:h> Most HTTP/1.0 caches will not recognize or obey 
    1412       this directive. Also, no-cache response directives with field-names are 
    1413       often handled by implementations as if an unqualified no-cache directive 
    1414       was received; i.e., the special handling for the qualified form is not 
    1415       widely implemented.</t> 
    14161432   </list> 
    14171433</t> 
    14181434<t> 
    1419    <x:dfn>no-store</x:dfn> 
     1435   The no-cache response directive indicates that the response &MUST-NOT; 
     1436   be used to satisfy a subsequent request without successful validation on 
     1437   the origin server. This allows an origin server to prevent a cache from 
     1438   using it to satisfy a request without contacting it, even by caches that 
     1439   have been configured to return stale responses. 
     1440</t> 
     1441<t> 
     1442   If the no-cache response directive specifies one or more field-names, 
     1443   then a cache &MAY; use the response to satisfy a subsequent request, 
     1444   subject to any other restrictions on caching. However, any header fields 
     1445   in the response that have the field-name(s) listed &MUST-NOT; be sent 
     1446   in the response to a subsequent request without successful revalidation 
     1447   with the origin server. This allows an origin server to prevent the 
     1448   re-use of certain header fields in a response, while still allowing 
     1449   caching of the rest of the response. 
     1450</t>  
     1451<t> 
     1452   The field-names given are not limited to the set of standard header 
     1453   fields defined by this specification. Field names are case-insensitive. 
     1454</t> 
     1455<t> 
     1456   <x:h>Note:</x:h> Most HTTP/1.0 caches will not recognize or obey 
     1457   this directive. Also, no-cache response directives with field-names are 
     1458   often handled by implementations as if an unqualified no-cache directive 
     1459   was received; i.e., the special handling for the qualified form is not 
     1460   widely implemented. 
     1461</t> 
     1462<t> 
     1463   <x:h>Note:</x:h> For compatibility with non-robust recipients, even a 
     1464   single-entry list of field names &SHOULD; be sent using the quoted-string 
     1465   syntax. 
     1466</t> 
     1467</section> 
     1468 
     1469<section title="no-store" anchor="cache-response-directive.no-store"> 
    14201470   <iref item="Cache Directives" primary="true" subitem="no-store" /> 
    14211471   <iref item="no-store" primary="true" subitem="Cache Directive" /> 
    1422    <list> 
    1423       <t>The no-store response directive indicates that a cache &MUST-NOT; 
    1424       store any part of either the immediate request or response. This 
    1425       directive applies to both private and shared caches. "&MUST-NOT; 
    1426       store" in this context means that the cache &MUST-NOT; intentionally 
    1427       store the information in non-volatile storage, and &MUST; make a 
    1428       best-effort attempt to remove the information from volatile storage as 
    1429       promptly as possible after forwarding it.</t> 
    1430       <t>This directive is NOT a reliable or sufficient mechanism for ensuring 
    1431       privacy. In particular, malicious or compromised caches might not 
    1432       recognize or obey this directive, and communications networks might be 
    1433       vulnerable to eavesdropping.</t> 
    1434    </list> 
     1472<t> 
     1473   The no-store response directive indicates that a cache &MUST-NOT; 
     1474   store any part of either the immediate request or response. This 
     1475   directive applies to both private and shared caches. "&MUST-NOT; 
     1476   store" in this context means that the cache &MUST-NOT; intentionally 
     1477   store the information in non-volatile storage, and &MUST; make a 
     1478   best-effort attempt to remove the information from volatile storage as 
     1479   promptly as possible after forwarding it. 
    14351480</t> 
    14361481<t> 
    1437    <x:dfn>must-revalidate</x:dfn> 
     1482   This directive is NOT a reliable or sufficient mechanism for ensuring 
     1483   privacy. In particular, malicious or compromised caches might not 
     1484   recognize or obey this directive, and communications networks might be 
     1485   vulnerable to eavesdropping. 
     1486</t> 
     1487</section> 
     1488 
     1489<section title="must-revalidate" anchor="cache-response-directive.must-revalidate"> 
    14381490   <iref item="Cache Directives" primary="true" subitem="must-revalidate" /> 
    14391491   <iref item="must-revalidate" primary="true" subitem="Cache Directive" /> 
    1440    <list> 
    1441       <t>The must-revalidate response directive indicates that once it has 
    1442       become stale, a cache &MUST-NOT; use the response to satisfy subsequent 
    1443       requests without successful validation on the origin server.</t> 
    1444       <t>The must-revalidate directive is necessary to support reliable 
    1445       operation for certain protocol features. In all circumstances a 
    1446       cache &MUST; obey the must-revalidate directive; in particular, 
    1447       if a cache cannot reach the origin server for any reason, it &MUST; 
    1448       generate a 504 (Gateway Timeout) response.</t> 
    1449       <t>The must-revalidate directive ought to be used by servers if and only 
    1450       if failure to validate a request on the representation could result in 
    1451       incorrect operation, such as a silently unexecuted financial 
    1452       transaction.</t> 
    1453    </list> 
     1492<t> 
     1493   The must-revalidate response directive indicates that once it has 
     1494   become stale, a cache &MUST-NOT; use the response to satisfy subsequent 
     1495   requests without successful validation on the origin server. 
    14541496</t> 
    14551497<t> 
    1456    <x:dfn>proxy-revalidate</x:dfn> 
     1498   The must-revalidate directive is necessary to support reliable 
     1499   operation for certain protocol features. In all circumstances a 
     1500   cache &MUST; obey the must-revalidate directive; in particular, 
     1501   if a cache cannot reach the origin server for any reason, it &MUST; 
     1502   generate a 504 (Gateway Timeout) response. 
     1503</t> 
     1504<t> 
     1505   The must-revalidate directive ought to be used by servers if and only 
     1506   if failure to validate a request on the representation could result in 
     1507   incorrect operation, such as a silently unexecuted financial 
     1508   transaction. 
     1509</t> 
     1510</section> 
     1511 
     1512<section title="proxy-revalidate" anchor="cache-response-directive.proxy-revalidate"> 
    14571513   <iref item="Cache Directives" primary="true" subitem="proxy-revalidate" /> 
    14581514   <iref item="proxy-revalidate" primary="true" subitem="Cache Directive" /> 
    1459    <list> 
    1460       <t>The proxy-revalidate response directive has the same meaning as the 
    1461       must-revalidate response directive, except that it does not apply to 
    1462       private caches.</t> 
    1463    </list> 
     1515<t> 
     1516   The proxy-revalidate response directive has the same meaning as the 
     1517   must-revalidate response directive, except that it does not apply to 
     1518   private caches. 
    14641519</t> 
    1465 <t> 
    1466    <x:dfn>max-age</x:dfn> 
     1520</section> 
     1521 
     1522<section title="max-age" anchor="cache-response-directive.max-age"> 
    14671523   <iref item="Cache Directives" primary="true" subitem="max-age" /> 
    14681524   <iref item="max-age" primary="true" subitem="Cache Directive" /> 
     1525<t> 
     1526   Argument syntax: 
    14691527   <list> 
    1470       <t>The max-age response directive indicates that the response is to be 
    1471       considered stale after its age is greater than the specified number of 
    1472       seconds.</t> 
     1528      <t> 
     1529        <x:ref>delta-seconds</x:ref> (see <xref target="delta-seconds"/>) 
     1530      </t> 
    14731531   </list> 
    14741532</t> 
    14751533<t> 
    1476    <x:dfn>s-maxage</x:dfn> 
     1534   The max-age response directive indicates that the response is to be 
     1535   considered stale after its age is greater than the specified number of 
     1536   seconds. 
     1537</t> 
     1538</section>       
     1539 
     1540<section title="s-maxage" anchor="cache-response-directive.s-maxage"> 
    14771541   <iref item="Cache Directives" primary="true" subitem="s-maxage" /> 
    14781542   <iref item="s-maxage" primary="true" subitem="Cache Directive" /> 
     1543<t> 
     1544   Argument syntax: 
    14791545   <list> 
    1480       <t>The s-maxage response directive indicates that, in shared caches, the 
    1481       maximum age specified by this directive overrides the maximum age 
    1482       specified by either the max-age directive or the Expires header field. The 
    1483       s-maxage directive also implies the semantics of the proxy-revalidate 
    1484       response directive.</t> 
     1546      <t> 
     1547        <x:ref>delta-seconds</x:ref> (see <xref target="delta-seconds"/>) 
     1548      </t> 
    14851549   </list> 
    14861550</t> 
    14871551<t> 
    1488    <x:dfn>no-transform</x:dfn> 
     1552   The s-maxage response directive indicates that, in shared caches, the 
     1553   maximum age specified by this directive overrides the maximum age 
     1554   specified by either the max-age directive or the Expires header field. The 
     1555   s-maxage directive also implies the semantics of the proxy-revalidate 
     1556   response directive. 
     1557</t> 
     1558</section> 
     1559 
     1560<section title="no-transform" anchor="cache-response-directive.no-transform"> 
    14891561   <iref item="Cache Directives" primary="true" subitem="no-transform" /> 
    14901562   <iref item="no-transform" primary="true" subitem="Cache Directive" /> 
    1491    <list> 
    1492       <t>The no-transform response directive indicates that an intermediary 
    1493       (regardless of whether it implements a cache) &MUST-NOT; change the  
    1494       Content-Encoding, Content-Range or Content-Type response header fields,  
    1495       nor the response representation.</t> 
    1496    </list> 
     1563<t> 
     1564   The no-transform response directive indicates that an intermediary 
     1565   (regardless of whether it implements a cache) &MUST-NOT; change the  
     1566   Content-Encoding, Content-Range or Content-Type response header fields,  
     1567   nor the response representation. 
    14971568</t> 
     1569</section> 
    14981570 
    14991571</section> 
    15001572