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/p6-cache.xml

    r1707 r1708  
    508508   response header block has been received, a cache &MAY; store an incomplete
    509509   response message body if the cache entry is recorded as incomplete.
    510    Likewise, a 206 (Partial Content) response &MAY; be stored as if it were
     510   Likewise, a <x:ref>206 (Partial Content)</x:ref> response &MAY; be stored as if it were
    511511   an incomplete 200 (OK) cache entry.  However, a cache &MUST-NOT; store
    512512   incomplete or partial content responses if it does not support the Range
     
    522522   specifies a range that is wholly within the incomplete response.
    523523   A cache &MUST-NOT; send a partial response to a client without explicitly
    524    marking it as such using the 206 (Partial Content) status code.
     524   marking it as such using the <x:ref>206 (Partial Content)</x:ref> status code.
    525525</t>
    526526</section>
     
    866866<t>
    867867   If a cache receives a first-hand response (either an entire response, or a
    868    304 (Not Modified) response) that it would normally forward to the
     868   <x:ref>304 (Not Modified)</x:ref> response) that it would normally forward to the
    869869   requesting client, and the received response is no longer fresh, the cache
    870870   can forward it to the requesting client without adding a new Warning (but
     
    906906   <list style="symbols">
    907907      <t>
    908          A 304 (Not Modified) response status code indicates that the stored
     908         A <x:ref>304 (Not Modified)</x:ref> response status code indicates that the stored
    909909         response can be updated and reused; see <xref
    910910         target="freshening.responses"/>.
     
    928928<section anchor="freshening.responses" title="Freshening Responses with 304 Not Modified">
    929929<t>
    930    When a cache receives a 304 (Not Modified) response and already has one
     930   When a cache receives a <x:ref>304 (Not Modified)</x:ref> response and already has one
    931931   or more stored 200 (OK) responses for the same cache key, the cache needs
    932932   to identify which of the stored responses are updated by this new response
     
    23082308    </front>
    23092309    <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;" />
    2310     <x:source basename="p4-conditional" href="p4-conditional.xml" />
     2310    <x:source basename="p4-conditional" href="p4-conditional.xml">
     2311      <x:defines>304 (Not Modified)</x:defines>
     2312    </x:source>
    23112313  </reference>
    23122314
     
    23292331    </front>
    23302332    <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;" />
    2331     <x:source basename="p5-range" href="p5-range.xml" />
     2333    <x:source basename="p5-range" href="p5-range.xml">
     2334      <x:defines>206 (Partial Content)</x:defines>
     2335    </x:source>
    23322336  </reference>
    23332337
Note: See TracChangeset for help on using the changeset viewer.