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

Timestamp:

08/07/12 13:29:53 (10 years ago)

Author:

julian.reschke@…

Message:

Work-in-progress: hyperlink header field definitions(P5)

File:

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

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

@@ -510 +510 @@
    Likewise, a <x:ref>206 (Partial Content)</x:ref> response &MAY; be stored as if it were
    an incomplete <x:ref>200 (OK)</x:ref> cache entry.  However, a cache &MUST-NOT; store
-   incomplete or partial content responses if it does not support the Range
-   and Content-Range header fields or if it does not understand the
-   range units used in those fields.
+   incomplete or partial content responses if it does not support the
+   <x:ref>Range</x:ref> and <x:ref>Content-Range</x:ref> header fields or if it
+   does not understand the range units used in those fields.
 </t>
 <t>
@@ -1149 +1149 @@
          with warn-code 2xx; and,</t>
       <t>use other header fields provided in the new response, aside
-         from Content-Range, to replace all instances of the corresponding
-         header fields in the stored response.</t>
+         from <x:ref>Content-Range</x:ref>, to replace all instances of the
+         corresponding header fields in the stored response.</t>
    </list>
 </t>
@@ -1358 +1358 @@
    The no-transform request directive indicates that an intermediary
    (whether or not it implements a cache) &MUST-NOT; change the 
-   Content-Encoding, Content-Range or Content-Type request header fields, 
-   nor the request representation.
+   Content-Encoding, <x:ref>Content-Range</x:ref> or Content-Type request
+   header fields, nor the request representation.
 </t>
 </section>
@@ -1587 +1587 @@
    The no-transform response directive indicates that an intermediary
    (regardless of whether it implements a cache) &MUST-NOT; change the 
-   Content-Encoding, Content-Range or Content-Type response header fields, 
-   nor the response representation.
+   Content-Encoding, <x:ref>Content-Range</x:ref> or Content-Type response
+   header fields, nor the response representation.
 </t>
 </section>
@@ -2354 +2354 @@
     <x:source basename="p5-range" href="p5-range.xml">
       <x:defines>206 (Partial Content)</x:defines>
+      <x:defines>Content-Range</x:defines>
+      <x:defines>Range</x:defines>
     </x:source>
   </reference>