Changeset 1727 for draft-ietf-httpbis/latest/p6-cache.html

Timestamp:

Jul 5, 2012, 10:06:19 AM (8 years ago)

Author:

julian.reschke@…

Message:

Work-in-progress: hyperlink status code range definitions

File:

• draft-ietf-httpbis/latest/p6-cache.html (modified) (1 diff)

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

@@ -1149 +1149 @@
       <p id="rfc.section.2.6.p.4">A cache <em class="bcp14">MUST</em> invalidate the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) when it receives a non-error response to a request with a method whose safety is unknown.
       </p>
-      <p id="rfc.section.2.6.p.5">Here, a "non-error response" is one with a 2xx or 3xx status code. "Invalidate" means that the cache will either remove all
-         stored responses related to the effective request URI, or will mark these as "invalid" and in need of a mandatory validation
-         before they can be returned in response to a subsequent request.
+      <p id="rfc.section.2.6.p.5">Here, a "non-error response" is one with a <a href="p2-semantics.html#status.2xx" class="smpl">2xx</a> or <a href="p2-semantics.html#status.3xx" class="smpl">3xx</a> status code. "Invalidate" means that the cache will either remove all stored responses related to the effective request URI,
+         or will mark these as "invalid" and in need of a mandatory validation before they can be returned in response to a subsequent
+         request.
       </p>
       <p id="rfc.section.2.6.p.6">Note that this does not guarantee that all appropriate responses are invalidated. For example, the request that caused the