Changeset 1715 for draft-ietf-httpbis/latest/p6-cache.xml

Timestamp:

04/07/12 19:54:55 (9 years ago)

Author:

julian.reschke@…

Message:

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

File:

• draft-ietf-httpbis/latest/p6-cache.xml (modified) (4 diffs)

draft-ietf-httpbis/latest/p6-cache.xml

@@ -432 +432 @@
    HTTP responses corresponding to prior requests that used the same key.
    The most common form of cache entry is a successful result of a retrieval
-   request: i.e., a 200 (OK) response containing a representation of the
-   resource identified by the request target.  However, it is also possible
+   request: i.e., a <x:ref>200 (OK)</x:ref> response containing a representation
+   of the resource identified by the request target.  However, it is also possible
    to cache negative results (e.g., <x:ref>404 (Not Found)</x:ref>, incomplete results
    (e.g., <x:ref>206 (Partial Content)</x:ref>), and responses to safe methods other than
@@ -504 +504 @@
    A response message is considered complete when all of the octets
    indicated by the message framing (&messaging;) are received
-   prior to the connection being closed.
-   If the request is GET, the response status is 200 (OK), and the entire
+   prior to the connection being closed. If the request is GET, the response
+   status is <x:ref>200 (OK)</x:ref>, and the entire
    response header block has been received, a cache &MAY; store an incomplete
    response message body if the cache entry is recorded as incomplete.
    Likewise, a <x:ref>206 (Partial Content)</x:ref> response &MAY; be stored as if it were
-   an incomplete 200 (OK) cache entry.  However, a cache &MUST-NOT; store
+   an incomplete <x:ref>200 (OK)</x:ref> cache entry.  However, a cache &MUST-NOT; store
    incomplete or partial content responses if it does not support the Range
    and Content-Range header fields or if it does not understand the
@@ -929 +929 @@
 <t>
    When a cache receives a <x:ref>304 (Not Modified)</x:ref> response and already has one
-   or more stored 200 (OK) responses for the same cache key, the cache needs
+   or more stored <x:ref>200 (OK)</x:ref> responses for the same cache key, the cache needs
    to identify which of the stored responses are updated by this new response
    and then update the stored response(s) with the new information provided in
@@ -2288 +2288 @@
     <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;" />
     <x:source basename="p2-semantics" href="p2-semantics.xml">
+      <x:defines>200 (OK)</x:defines>
       <x:defines>404 (Not Found)</x:defines>
       <x:defines>504 (Gateway Timeout)</x:defines>