Ignore:
Timestamp:
Jul 6, 2012, 7:48:51 AM (7 years ago)
Author:
julian.reschke@…
Message:

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

File:
1 edited

Legend:

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

    r1734 r1735  
    683683   If no explicit expiration time is present in a stored response that has a
    684684   status code whose definition allows heuristic freshness to be used
    685    (including the following in &status-codes;: 200, 203, <x:ref>206</x:ref>, 300, 301 and
    686    410), a cache &MAY; calculate a heuristic expiration time. A cache &MUST-NOT;
     685   (including the following in &status-codes;: <x:ref>200 (OK)</x:ref>, <x:ref>203
     686   (Non-Authoritative Information)</x:ref>, <x:ref>206 (Partial Content)</x:ref>,
     687   <x:ref>300 (Multiple Choices)</x:ref>, <x:ref>301 (Moved Permanently)</x:ref> and
     688   <x:ref>410 (Gone)</x:ref>), a cache &MAY; calculate a heuristic expiration time. A cache &MUST-NOT;
    687689   use heuristics to determine freshness for responses with status codes that do
    688690   not explicitly allow it.
     
    923925      </t>
    924926      <t>
    925          However, if a cache receives a 5xx response while attempting to
    926          validate a response, it can either forward this response to the
    927          requesting client, or act as if the server failed to respond. In the
    928          latter case, it can return a previously stored response (see <xref
    929          target="serving.stale.responses" />).
     927         However, if a cache receives a <x:ref>5xx (Server Error)</x:ref>
     928         response while attempting to validate a response, it can either
     929         forward this response to the requesting client, or act as if the
     930         server failed to respond. In the latter case, it can return a
     931         previously stored response (see <xref target="serving.stale.responses" />).
    930932      </t>
    931933   </list>
     
    10331035</t>
    10341036<t>
    1035    Here, a "non-error response" is one with a <x:ref>2xx</x:ref> or <x:ref>3xx</x:ref> status code.
     1037   Here, a "non-error response" is one with a <x:ref>2xx (Successful)</x:ref> or
     1038   <x:ref>3xx (Redirection)</x:ref> status code.
    10361039   "Invalidate" means that the cache will either remove all stored
    10371040   responses related to the effective request URI, or will mark these as
     
    22942297    <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;" />
    22952298    <x:source basename="p2-semantics" href="p2-semantics.xml">
    2296       <x:defines>2xx</x:defines>
     2299      <x:defines>2xx (Successful)</x:defines>
    22972300      <x:defines>200 (OK)</x:defines>
    2298       <x:defines>3xx</x:defines>
     2301      <x:defines>203 (Non-Authoritative Information)</x:defines>
     2302      <x:defines>3xx (Redirection)</x:defines>
     2303      <x:defines>300 (Multiple Choices)</x:defines>
     2304      <x:defines>301 (Moved Permanently)</x:defines>
    22992305      <x:defines>404 (Not Found)</x:defines>
     2306      <x:defines>410 (Gone)</x:defines>
     2307      <x:defines>5xx (Server Error)</x:defines>
    23002308      <x:defines>504 (Gateway Timeout)</x:defines>
    23012309    </x:source>
     
    23452353    <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;" />
    23462354    <x:source basename="p5-range" href="p5-range.xml">
    2347       <x:defines>206</x:defines>
    23482355      <x:defines>206 (Partial Content)</x:defines>
    23492356    </x:source>
Note: See TracChangeset for help on using the changeset viewer.