Changeset 782 for draft-ietf-httpbis

Timestamp:

Mar 9, 2010, 8:38:03 PM (10 years ago)

Author:

mnot@…

Message:

remove ambiguous comma from definition of a stale response.

Location:

draft-ietf-httpbis/latest

Files:

• p6-cache.html (modified) (1 diff)
• p6-cache.xml (modified) (1 diff)

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

@@ -905 +905 @@
   current_age   = corrected_initial_age + resident_time;
 </pre><h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;<a id="serving.stale.responses" href="#serving.stale.responses">Serving Stale Responses</a></h3>
-      <p id="rfc.section.2.3.3.p.1">A "stale" response is one that either has explicit expiry information, or is allowed to have heuristic expiry calculated,
-         but is not fresh according to the calculations in <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>.
+      <p id="rfc.section.2.3.3.p.1">A "stale" response is one that either has explicit expiry information or is allowed to have heuristic expiry calculated, but
+         is not fresh according to the calculations in <a href="#expiration.model" title="Freshness Model">Section&nbsp;2.3</a>.
       </p>
       <p id="rfc.section.2.3.3.p.2">Caches <em class="bcp14">MUST NOT</em> return a stale response if it is prohibited by an explicit in-protocol directive (e.g., by a "no-store" or "no-cache" cache

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

@@ -727 +727 @@
 <section anchor="serving.stale.responses" title="Serving Stale Responses">
 <t>
-  A "stale" response is one that either has explicit expiry information, or is allowed to
+  A "stale" response is one that either has explicit expiry information or is allowed to
   have heuristic expiry calculated, but is not fresh according to the calculations in
   <xref target="expiration.model" />.