Changeset 1708 for draft-ietf-httpbis/latest/p6-cache.xml

Timestamp:

Jul 3, 2012, 11:26:11 AM (7 years ago)

Author:

julian.reschke@…

Message:

Work-in-progress: hyperlink status codes definitions (for those defined in parts 4, 5, and 7)

File:

• draft-ietf-httpbis/latest/p6-cache.xml (modified) (7 diffs)

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

@@ -508 +508 @@
    response header block has been received, a cache &MAY; store an incomplete
    response message body if the cache entry is recorded as incomplete.
-   Likewise, a 206 (Partial Content) response &MAY; be stored as if it were
+   Likewise, a <x:ref>206 (Partial Content)</x:ref> response &MAY; be stored as if it were
    an incomplete 200 (OK) cache entry.  However, a cache &MUST-NOT; store
    incomplete or partial content responses if it does not support the Range
@@ -522 +522 @@
    specifies a range that is wholly within the incomplete response.
    A cache &MUST-NOT; send a partial response to a client without explicitly
-   marking it as such using the 206 (Partial Content) status code.
+   marking it as such using the <x:ref>206 (Partial Content)</x:ref> status code.
 </t>
 </section>
@@ -866 +866 @@
 <t>
    If a cache receives a first-hand response (either an entire response, or a
-   304 (Not Modified) response) that it would normally forward to the
+   <x:ref>304 (Not Modified)</x:ref> response) that it would normally forward to the
    requesting client, and the received response is no longer fresh, the cache
    can forward it to the requesting client without adding a new Warning (but
@@ -906 +906 @@
    <list style="symbols">
       <t>
-         A 304 (Not Modified) response status code indicates that the stored
+         A <x:ref>304 (Not Modified)</x:ref> response status code indicates that the stored
          response can be updated and reused; see <xref
          target="freshening.responses"/>.
@@ -928 +928 @@
 <section anchor="freshening.responses" title="Freshening Responses with 304 Not Modified">
 <t>
-   When a cache receives a 304 (Not Modified) response and already has one
+   When a cache receives a <x:ref>304 (Not Modified)</x:ref> response and already has one
    or more stored 200 (OK) responses for the same cache key, the cache needs
    to identify which of the stored responses are updated by this new response
@@ -2308 +2308 @@
     </front>
     <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;" />
-    <x:source basename="p4-conditional" href="p4-conditional.xml" />
+    <x:source basename="p4-conditional" href="p4-conditional.xml">
+      <x:defines>304 (Not Modified)</x:defines>
+    </x:source>
   </reference>
 
@@ -2329 +2331 @@
     </front>
     <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;" />
-    <x:source basename="p5-range" href="p5-range.xml" />
+    <x:source basename="p5-range" href="p5-range.xml">
+      <x:defines>206 (Partial Content)</x:defines>
+    </x:source>
   </reference>