Changeset 1708 for draft-ietf-httpbis/latest/p5-range.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/p5-range.xml (modified) (10 diffs)

draft-ietf-httpbis/latest/p5-range.xml

@@ -312 +312 @@
   <iref primary="true" item="206 Partial Content (status code)" x:for-anchor=""/>
   <iref primary="true" item="Status Codes" subitem="206 Partial Content" x:for-anchor=""/>
+  <x:anchor-alias value="206 (Partial Content)"/>
 <t>
    The server has fulfilled the partial GET request for the resource.
@@ -354 +355 @@
   <iref primary="true" item="416 Requested Range Not Satisfiable (status code)" x:for-anchor=""/>
   <iref primary="true" item="Status Codes" subitem="416 Requested Range Not Satisfiable" x:for-anchor=""/>
+  <x:anchor-alias value="416 (Requested Range Not Satisfiable)"/>
 <t>
    A server &SHOULD; return a response with this status code if a request
@@ -377 +379 @@
 <x:note>
   <t>
-    &Note; Clients cannot depend on servers to send a 416 (Requested
-    range not satisfiable) response instead of a 200 (OK) response for
+    &Note; Clients cannot depend on servers to send a <x:ref>416 (Requested
+    Range Not Satisfiable)</x:ref> response instead of a 200 (OK) response for
     an unsatisfiable Range header field, since not all servers
     implement this header field.
@@ -442 +444 @@
 </t>
 <t>
-   When a client receives an incomplete 200 (OK) or 206 (Partial Content)
+   When a client receives an incomplete 200 (OK) or <x:ref>206 (Partial Content)</x:ref>
    response and already has one or more stored responses for the same method
    and effective request URI, all of the stored responses with the same
@@ -456 +458 @@
 </t>
 <t>
-   If the new response is a 206 (Partial Content) response and at least one
+   If the new response is a <x:ref>206 (Partial Content)</x:ref> response and at least one
    of the matching stored responses is a 200 (OK), then the combined response
    header fields consist of the most recent 200 response's header fields.
@@ -578 +580 @@
 <t>
    In the case of a byte range request:
-   A server sending a response with status code 416 (Requested range not
-   satisfiable) &SHOULD; include a Content-Range field with a byte-range-resp-spec
+   A server sending a response with status code <x:ref>416 (Requested Range Not
+   Satisfiable)</x:ref> &SHOULD; include a Content-Range field with a byte-range-resp-spec
    of "*". The instance-length specifies the current length of
-   the selected resource. A response with status code 206 (Partial
-   Content) &MUST-NOT; include a Content-Range field with a byte-range-resp-spec of "*".
+   the selected resource. A response with status code <x:ref>206 (Partial Content)</x:ref>
+   &MUST-NOT; include a Content-Range field with a byte-range-resp-spec of "*".
 </t>
 <t>
   The "Content-Range" header field has no meaning for status codes that do not 
   explicitly describe its semantic. Currently, only status codes
-  206 (Partial Content) and 416 (Requested range not satisfiable) describe
+  <x:ref>206 (Partial Content)</x:ref> and <x:ref>416 (Requested Range Not Satisfiable)</x:ref> describe
   the meaning of this header field.
 </t>
@@ -678 +680 @@
    validator for the selected representation of the target resource, then
    the server &SHOULD; send the specified sub-range of the representation
-   using a 206 (Partial Content) response. If the validator does not match,
+   using a <x:ref>206 (Partial Content)</x:ref> response. If the validator does not match,
    then the server &SHOULD; send the entire representation using a 200 (OK)
    response.
@@ -760 +762 @@
    Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set
    is unsatisfiable, the server &SHOULD; return a response with a 
-   416 (Requested range not satisfiable) status code. Otherwise, the server
-   &SHOULD; return a response with a 206 (Partial Content) status code
+   <x:ref>416 (Requested Range Not Satisfiable)</x:ref> status code. Otherwise, the server
+   &SHOULD; return a response with a <x:ref>206 (Partial Content)</x:ref> status code
    containing the satisfiable ranges of the representation.
 </t>
@@ -830 +832 @@
      <t>The presence of a Range header field in an unconditional GET modifies
         what is returned if the GET is otherwise successful. In other
-        words, the response carries a status code of 206 (Partial
-        Content) instead of 200 (OK).</t>
+        words, the response carries a status code of <x:ref>206 (Partial Content)</x:ref>
+        instead of 200 (OK).</t>
 
      <t>The presence of a Range header field in a conditional GET (a request
@@ -1221 +1223 @@
 <iref item="multipart/byteranges Media Type" primary="true"/>
 <t>
-   When an HTTP 206 (Partial Content) response message includes the
+   When an HTTP <x:ref>206 (Partial Content)</x:ref> response message includes the
    content of multiple ranges (a response to a request for multiple
    non-overlapping ranges), these are transmitted as a multipart