Ignore:
Timestamp:
Jul 23, 2010, 5:29:48 AM (9 years ago)
Author:
mnot@…
Message:

Add heuristic freshness requirements to status codes (see #199).

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r874 r884  
    7474  <!ENTITY p5-status-codes            "<xref target='Part5' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    7575  <!ENTITY p7-status-codes            "<xref target='Part7' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     76  <!ENTITY p6-heuristic               "<xref target='Part6' x:rel='#heuristic.freshness'
     77xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    7678]>
    7779<?rfc toc="yes" ?>
     
    11811183  </list>
    11821184</t>
     1185<t>
     1186        Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
     1187        freshness for 200 responses.
     1188</t>
    11831189</section>
    11841190
     
    12411247   response would otherwise be 200 (OK).
    12421248</t>
     1249<t>
     1250        Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
     1251        freshness for 203 responses.
     1252</t>
     1253
    12431254</section>
    12441255
     
    12941305   and the enclosed payload is a partial representation as defined in &status-206;.
    12951306</t>
     1307<t>
     1308        Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
     1309        freshness for 206 responses.
     1310</t>
    12961311</section>
    12971312</section>
     
    13401355   include the specific URI for that representation in the Location
    13411356   field; user agents &MAY; use the Location field value for automatic
    1342    redirection. This response is cacheable unless indicated otherwise.
    1343 </t>
     1357   redirection.
     1358</t>
     1359<t>
     1360        Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
     1361        freshness for 300 responses.
     1362</t>
     1363
    13441364</section>
    13451365
     
    13521372   URIs.  Clients with link editing capabilities ought to automatically
    13531373   re-link references to the Effective Request URI to one or more of the new
    1354    references returned by the server, where possible. This response is
    1355    cacheable unless indicated otherwise.
     1374   references returned by the server, where possible.
     1375</t>
     1376<t>
     1377        Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
     1378        freshness for 301 responses.
    13561379</t>
    13571380<t>
     
    13841407   The requested resource resides temporarily under a different URI.
    13851408   Since the redirection might be altered on occasion, the client &SHOULD;
    1386    continue to use the Effectice Request URI for future requests.  This response
    1387    is only cacheable if indicated by a Cache-Control or Expires header
    1388    field.
     1409   continue to use the Effectice Request URI for future requests.
    13891410</t>
    13901411<t>
     
    14541475</t>
    14551476<t>
    1456    A 303 response &SHOULD-NOT; be cached unless it is indicated as
    1457    cacheable by Cache-Control or Expires header fields.  Except for
    1458    responses to a HEAD request, the representation of a 303 response &SHOULD;
    1459    contain a short hypertext note with a hyperlink to the Location URI.
     1477   Except for responses to a HEAD request, the representation of a 303
     1478   response &SHOULD; contain a short hypertext note with a hyperlink
     1479   to the Location URI.
    14601480</t>
    14611481</section>
     
    14971517   The requested resource resides temporarily under a different URI.
    14981518   Since the redirection &MAY; be altered on occasion, the client &SHOULD;
    1499    continue to use the Effective Request URI for future requests.  This response
    1500    is only cacheable if indicated by a Cache-Control or Expires header
    1501    field.
     1519   continue to use the Effective Request URI for future requests.
    15021520</t>
    15031521<t>
     
    16971715   server does not know, or has no facility to determine, whether or not
    16981716   the condition is permanent, the status code 404 (Not Found) &SHOULD; be
    1699    used instead. This response is cacheable unless indicated otherwise.
     1717   used instead.
    17001718</t>
    17011719<t>
     
    17101728   discretion of the server owner.
    17111729</t>
     1730<t>
     1731        Caches &MAY; use a heuristic (see &p6-heuristic;) to determine freshness
     1732        for 410 responses.
     1733</t>
     1734
    17121735</section>
    17131736
Note: See TracChangeset for help on using the changeset viewer.