Ignore:
Timestamp:
Jul 4, 2012, 12:54:55 PM (7 years ago)
Author:
julian.reschke@…
Message:

Work-in-progress: hyperlink status codes definitions (2xx range)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.xml

    r1713 r1715  
    432432   HTTP responses corresponding to prior requests that used the same key.
    433433   The most common form of cache entry is a successful result of a retrieval
    434    request: i.e., a 200 (OK) response containing a representation of the
    435    resource identified by the request target.  However, it is also possible
     434   request: i.e., a <x:ref>200 (OK)</x:ref> response containing a representation
     435   of the resource identified by the request target.  However, it is also possible
    436436   to cache negative results (e.g., <x:ref>404 (Not Found)</x:ref>, incomplete results
    437437   (e.g., <x:ref>206 (Partial Content)</x:ref>), and responses to safe methods other than
     
    504504   A response message is considered complete when all of the octets
    505505   indicated by the message framing (&messaging;) are received
    506    prior to the connection being closed.
    507    If the request is GET, the response status is 200 (OK), and the entire
     506   prior to the connection being closed. If the request is GET, the response
     507   status is <x:ref>200 (OK)</x:ref>, and the entire
    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.
    510510   Likewise, a <x:ref>206 (Partial Content)</x:ref> response &MAY; be stored as if it were
    511    an incomplete 200 (OK) cache entry.  However, a cache &MUST-NOT; store
     511   an incomplete <x:ref>200 (OK)</x:ref> cache entry.  However, a cache &MUST-NOT; store
    512512   incomplete or partial content responses if it does not support the Range
    513513   and Content-Range header fields or if it does not understand the
     
    929929<t>
    930930   When a cache receives a <x:ref>304 (Not Modified)</x:ref> response and already has one
    931    or more stored 200 (OK) responses for the same cache key, the cache needs
     931   or more stored <x:ref>200 (OK)</x:ref> responses for the same cache key, the cache needs
    932932   to identify which of the stored responses are updated by this new response
    933933   and then update the stored response(s) with the new information provided in
     
    22882288    <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;" />
    22892289    <x:source basename="p2-semantics" href="p2-semantics.xml">
     2290      <x:defines>200 (OK)</x:defines>
    22902291      <x:defines>404 (Not Found)</x:defines>
    22912292      <x:defines>504 (Gateway Timeout)</x:defines>
Note: See TracChangeset for help on using the changeset viewer.