Ignore:
Timestamp:
Jul 5, 2012, 11:32:41 PM (7 years ago)
Author:
julian.reschke@…
Message:

Work-in-progress: hyperlink status codes definitions (P5)

File:
1 edited

Legend:

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

    r1726 r1732  
    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"/>
    314315  <x:anchor-alias value="206 (Partial Content)"/>
    315316<t>
     
    461462   of the matching stored responses is a <x:ref>200 (OK)</x:ref>, then the combined response
    462463   header fields consist of the most recent 200 response's header fields.
    463    If all of the matching stored responses are 206 responses, then the
     464   If all of the matching stored responses are <x:ref>206</x:ref> responses, then the
    464465   stored response with the most header fields is used as the source of
    465466   header fields for the combined response, except that the client &MUST;
     
    478479   incomplete.  If the union consists of a discontinuous range of the
    479480   representation, then the client &MAY; store it as either a multipart range
    480    response or as multiple 206 responses with one continuous range each.
     481   response or as multiple <x:ref>206</x:ref> responses with one continuous range each.
    481482</t>
    482483</section>
     
    13521353<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
    13531354<t>
    1354   Clarify that it is not ok to use a weak validator in a 206 response.
     1355  Clarify that it is not ok to use a weak validator in a <x:ref>206</x:ref> response.
    13551356  (<xref target="status.206"/>)
    13561357</t>
Note: See TracChangeset for help on using the changeset viewer.