Ignore:
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:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.xml

    r1697 r1708  
    312312  <iref primary="true" item="206 Partial Content (status code)" x:for-anchor=""/>
    313313  <iref primary="true" item="Status Codes" subitem="206 Partial Content" x:for-anchor=""/>
     314  <x:anchor-alias value="206 (Partial Content)"/>
    314315<t>
    315316   The server has fulfilled the partial GET request for the resource.
     
    354355  <iref primary="true" item="416 Requested Range Not Satisfiable (status code)" x:for-anchor=""/>
    355356  <iref primary="true" item="Status Codes" subitem="416 Requested Range Not Satisfiable" x:for-anchor=""/>
     357  <x:anchor-alias value="416 (Requested Range Not Satisfiable)"/>
    356358<t>
    357359   A server &SHOULD; return a response with this status code if a request
     
    377379<x:note>
    378380  <t>
    379     &Note; Clients cannot depend on servers to send a 416 (Requested
    380     range not satisfiable) response instead of a 200 (OK) response for
     381    &Note; Clients cannot depend on servers to send a <x:ref>416 (Requested
     382    Range Not Satisfiable)</x:ref> response instead of a 200 (OK) response for
    381383    an unsatisfiable Range header field, since not all servers
    382384    implement this header field.
     
    442444</t>
    443445<t>
    444    When a client receives an incomplete 200 (OK) or 206 (Partial Content)
     446   When a client receives an incomplete 200 (OK) or <x:ref>206 (Partial Content)</x:ref>
    445447   response and already has one or more stored responses for the same method
    446448   and effective request URI, all of the stored responses with the same
     
    456458</t>
    457459<t>
    458    If the new response is a 206 (Partial Content) response and at least one
     460   If the new response is a <x:ref>206 (Partial Content)</x:ref> response and at least one
    459461   of the matching stored responses is a 200 (OK), then the combined response
    460462   header fields consist of the most recent 200 response's header fields.
     
    578580<t>
    579581   In the case of a byte range request:
    580    A server sending a response with status code 416 (Requested range not
    581    satisfiable) &SHOULD; include a Content-Range field with a byte-range-resp-spec
     582   A server sending a response with status code <x:ref>416 (Requested Range Not
     583   Satisfiable)</x:ref> &SHOULD; include a Content-Range field with a byte-range-resp-spec
    582584   of "*". The instance-length specifies the current length of
    583    the selected resource. A response with status code 206 (Partial
    584    Content) &MUST-NOT; include a Content-Range field with a byte-range-resp-spec of "*".
     585   the selected resource. A response with status code <x:ref>206 (Partial Content)</x:ref>
     586   &MUST-NOT; include a Content-Range field with a byte-range-resp-spec of "*".
    585587</t>
    586588<t>
    587589  The "Content-Range" header field has no meaning for status codes that do not
    588590  explicitly describe its semantic. Currently, only status codes
    589   206 (Partial Content) and 416 (Requested range not satisfiable) describe
     591  <x:ref>206 (Partial Content)</x:ref> and <x:ref>416 (Requested Range Not Satisfiable)</x:ref> describe
    590592  the meaning of this header field.
    591593</t>
     
    678680   validator for the selected representation of the target resource, then
    679681   the server &SHOULD; send the specified sub-range of the representation
    680    using a 206 (Partial Content) response. If the validator does not match,
     682   using a <x:ref>206 (Partial Content)</x:ref> response. If the validator does not match,
    681683   then the server &SHOULD; send the entire representation using a 200 (OK)
    682684   response.
     
    760762   Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set
    761763   is unsatisfiable, the server &SHOULD; return a response with a
    762    416 (Requested range not satisfiable) status code. Otherwise, the server
    763    &SHOULD; return a response with a 206 (Partial Content) status code
     764   <x:ref>416 (Requested Range Not Satisfiable)</x:ref> status code. Otherwise, the server
     765   &SHOULD; return a response with a <x:ref>206 (Partial Content)</x:ref> status code
    764766   containing the satisfiable ranges of the representation.
    765767</t>
     
    830832     <t>The presence of a Range header field in an unconditional GET modifies
    831833        what is returned if the GET is otherwise successful. In other
    832         words, the response carries a status code of 206 (Partial
    833         Content) instead of 200 (OK).</t>
     834        words, the response carries a status code of <x:ref>206 (Partial Content)</x:ref>
     835        instead of 200 (OK).</t>
    834836
    835837     <t>The presence of a Range header field in a conditional GET (a request
     
    12211223<iref item="multipart/byteranges Media Type" primary="true"/>
    12221224<t>
    1223    When an HTTP 206 (Partial Content) response message includes the
     1225   When an HTTP <x:ref>206 (Partial Content)</x:ref> response message includes the
    12241226   content of multiple ranges (a response to a request for multiple
    12251227   non-overlapping ranges), these are transmitted as a multipart
Note: See TracChangeset for help on using the changeset viewer.