Changeset 1779

Timestamp:

Jul 14, 2012, 11:33:38 AM (7 years ago)

Author:

julian.reschke@…

Message:

dquote cache directive names in introductory sentences

Location:

draft-ietf-httpbis/latest

Files:

• p6-cache.html (modified) (14 diffs)
• p6-cache.xml (modified) (19 diffs)

draft-ietf-httpbis/latest/p6-cache.html

@@ -1259 +1259 @@
       <div id="rfc.iref.n.1"></div>
       <h4 id="rfc.section.7.2.1.1"><a href="#rfc.section.7.2.1.1">7.2.1.1</a>&nbsp;<a id="cache-request-directive.no-cache" href="#cache-request-directive.no-cache">no-cache</a></h4>
-      <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.
+      <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.
       </p>
       <div id="rfc.iref.c.8"></div>
       <div id="rfc.iref.n.2"></div>
       <h4 id="rfc.section.7.2.1.2"><a href="#rfc.section.7.2.1.2">7.2.1.2</a>&nbsp;<a id="cache-request-directive.no-store" href="#cache-request-directive.no-store">no-store</a></h4>
-      <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.
+      <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.
       </p>
       <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>
       </ul>
-      <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
-         number of seconds. Unless the max-stale request directive is also present, the client is not willing to accept a stale response.
+      <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 number of seconds. Unless the max-stale request directive is also present, the client is not willing to accept a
+         stale response.
       </p>
       <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>
       </ul>
-      <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
+      <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
          time. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its expiration time
          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>
       </ul>
-      <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 less
-         than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh for
-         at least the specified number of seconds.
+      <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
+         less than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh
+         for at least the specified number of seconds.
       </p>
       <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>
       <h4 id="rfc.section.7.2.1.6"><a href="#rfc.section.7.2.1.6">7.2.1.6</a>&nbsp;<a id="cache-request-directive.no-transform" href="#cache-request-directive.no-transform">no-transform</a></h4>
-      <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.
+      <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.
       </p>
       <div id="rfc.iref.c.13"></div>
       <div id="rfc.iref.o.1"></div>
       <h4 id="rfc.section.7.2.1.7"><a href="#rfc.section.7.2.1.7">7.2.1.7</a>&nbsp;<a id="cache-request-directive.only-if-cached" href="#cache-request-directive.only-if-cached">only-if-cached</a></h4>
-      <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
+      <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
          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
             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>
       <h4 id="rfc.section.7.2.2.1"><a href="#rfc.section.7.2.2.1">7.2.2.1</a>&nbsp;<a id="cache-response-directive.only-if-cached" href="#cache-response-directive.only-if-cached">public</a></h4>
-      <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&nbsp;3.2</a>).
+      <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&nbsp;3.2</a>).
       </p>
       <div id="rfc.iref.c.15"></div>
@@ -1340 +1341 @@
          </li>
       </ul>
-      <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.
+      <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.
       </p>
       <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>
       </ul>
-      <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
+      <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
          prevent a cache from using it to satisfy a request without contacting it, even by caches that have been configured to return
          stale responses.
@@ -1382 +1383 @@
       <div id="rfc.iref.n.5"></div>
       <h4 id="rfc.section.7.2.2.4"><a href="#rfc.section.7.2.2.4">7.2.2.4</a>&nbsp;<a id="cache-response-directive.no-store" href="#cache-response-directive.no-store">no-store</a></h4>
-      <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.
+      <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.
       </p>
       <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>
       <h4 id="rfc.section.7.2.2.5"><a href="#rfc.section.7.2.2.5">7.2.2.5</a>&nbsp;<a id="cache-response-directive.must-revalidate" href="#cache-response-directive.must-revalidate">must-revalidate</a></h4>
-      <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.
+      <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.
       </p>
       <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>
       <h4 id="rfc.section.7.2.2.6"><a href="#rfc.section.7.2.2.6">7.2.2.6</a>&nbsp;<a id="cache-response-directive.proxy-revalidate" href="#cache-response-directive.proxy-revalidate">proxy-revalidate</a></h4>
-      <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
+      <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
          not apply to private caches.
       </p>
@@ -1412 +1413 @@
          </li>
       </ul>
-      <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
+      <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
          number of seconds.
       </p>
@@ -1425 +1426 @@
          </li>
       </ul>
-      <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 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.
+      <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
+         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.
       </p>
       <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>
       <h4 id="rfc.section.7.2.2.9"><a href="#rfc.section.7.2.2.9">7.2.2.9</a>&nbsp;<a id="cache-response-directive.no-transform" href="#cache-response-directive.no-transform">no-transform</a></h4>
-      <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.
+      <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.
       </p>
       <h3 id="rfc.section.7.2.3"><a href="#rfc.section.7.2.3">7.2.3</a>&nbsp;<a id="cache.control.extensions" href="#cache.control.extensions">Cache Control Extensions</a></h3>

draft-ietf-httpbis/latest/p6-cache.xml

@@ -552 +552 @@
    responses to be stored is present in the response.
 </t>
-
 <t>
    In this specification, the following <x:ref>Cache-Control</x:ref> response
@@ -558 +557 @@
    must-revalidate, public, s-maxage.
 </t>
-
 <t>
    Note that cached responses that contain the "must-revalidate" and/or
@@ -1272 +1270 @@
 </t>
 
-<section anchor="cache-request-directive" 
-   title="Request Cache-Control Directives">
+<section title="Request Cache-Control Directives" anchor="cache-request-directive">
 
 <section title="no-cache" anchor="cache-request-directive.no-cache">
@@ -1279 +1276 @@
    <iref item="no-cache" primary="true" subitem="Cache Directive" />
 <t>
-   The no-cache request directive indicates that a cache &MUST-NOT; 
+   The "no-cache" request directive indicates that a cache &MUST-NOT; 
    use a stored response to satisfy the request without successful 
    validation on the origin server.
@@ -1289 +1286 @@
    <iref item="no-store" primary="true" subitem="Cache Directive" />
 <t>
-   The no-store request directive indicates that a cache &MUST-NOT;
+   The "no-store" request directive indicates that a cache &MUST-NOT;
    store any part of either this request or any response to it. This
    directive applies to both private and shared caches. "&MUST-NOT;
@@ -1322 +1319 @@
 </t>
 <t>
-   The max-age request directive indicates that the client is unwilling to
+   The "max-age" request directive indicates that the client is unwilling to
    accept a response whose age is greater than the specified number of
    seconds. Unless the max-stale request directive is also present, the
@@ -1346 +1343 @@
 </t>
 <t>
-   The max-stale request directive indicates that the client is willing
+   The "max-stale" request directive indicates that the client is willing
    to accept a response that has exceeded its expiration time. If max-stale
    is assigned a value, then the client is willing to accept a response
@@ -1372 +1369 @@
 </t>
 <t>
-   The min-fresh request directive indicates that the client is willing
+   The "min-fresh" request directive indicates that the client is willing
    to accept a response whose freshness lifetime is no less than its
    current age plus the specified time in seconds. That is, the client
@@ -1389 +1386 @@
    <iref item="no-transform" primary="true" subitem="Cache Directive" />
 <t>
-   The no-transform request directive indicates that an intermediary
+   The "no-transform" request directive indicates that an intermediary
    (whether or not it implements a cache) &MUST-NOT; change the 
    <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" />
 <t>
-   The only-if-cached request directive indicates that the client only wishes
+   The "only-if-cached" request directive indicates that the client only wishes
    to obtain a stored response. If it receives this directive, a cache &SHOULD;
    either respond using a stored response that is consistent with the other
@@ -1420 +1417 @@
    <iref item="public" primary="true" subitem="Cache Directive" />
 <t>
-   The public response directive indicates that a response whose 
+   The "public" response directive indicates that a response whose 
    associated request contains an 'Authentication' header &MAY; be 
    stored (see <xref target="caching.authenticated.responses" />).
@@ -1438 +1435 @@
 </t>
 <t>
-   The private response directive indicates that the response message is
+   The "private" response directive indicates that the response message is
    intended for a single user and &MUST-NOT; be stored by a shared cache. A
    private cache &MAY; store the response.
@@ -1480 +1477 @@
 </t>
 <t>
-   The no-cache response directive indicates that the response &MUST-NOT;
+   The "no-cache" response directive indicates that the response &MUST-NOT;
    be used to satisfy a subsequent request without successful validation on
    the origin server. This allows an origin server to prevent a cache from
@@ -1518 +1515 @@
    <iref item="no-store" primary="true" subitem="Cache Directive" />
 <t>
-   The no-store response directive indicates that a cache &MUST-NOT;
+   The "no-store" response directive indicates that a cache &MUST-NOT;
    store any part of either the immediate request or response. This
    directive applies to both private and shared caches. "&MUST-NOT;
@@ -1538 +1535 @@
    <iref item="must-revalidate" primary="true" subitem="Cache Directive" />
 <t>
-   The must-revalidate response directive indicates that once it has
+   The "must-revalidate" response directive indicates that once it has
    become stale, a cache &MUST-NOT; use the response to satisfy subsequent
    requests without successful validation on the origin server.
@@ -1561 +1558 @@
    <iref item="proxy-revalidate" primary="true" subitem="Cache Directive" />
 <t>
-   The proxy-revalidate response directive has the same meaning as the
+   The "proxy-revalidate" response directive has the same meaning as the
    must-revalidate response directive, except that it does not apply to
    private caches.
@@ -1579 +1576 @@
 </t>
 <t>
-   The max-age response directive indicates that the response is to be
+   The "max-age" response directive indicates that the response is to be
    considered stale after its age is greater than the specified number of
    seconds.
@@ -1602 +1599 @@
 </t>
 <t>
-   The s-maxage response directive indicates that, in shared caches, the
+   The "s-maxage" response directive indicates that, in shared caches, the
    maximum age specified by this directive overrides the maximum age
    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" />
 <t>
-   The no-transform response directive indicates that an intermediary
+   The "no-transform" response directive indicates that an intermediary
    (regardless of whether it implements a cache) &MUST-NOT; change the 
    <x:ref>Content-Encoding</x:ref>, <x:ref>Content-Range</x:ref> or