Ignore:
Timestamp:
Mar 2, 2012, 4:16:57 PM (7 years ago)
Author:
mnot@…
Message:

Move cache-specific HEAD language to p6; fully specify effects on cache. Addresses #227.

File:
1 edited

Legend:

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

    r1552 r1554  
    8686  <!ENTITY p6-explicit                "<xref target='Part6' x:rel='#calculating.freshness.lifetime' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    8787  <!ENTITY p6-invalid                 "<xref target='Part6' x:rel='#invalidation.after.updates.or.deletions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     88  <!ENTITY p6-head                 "<xref target='Part6' x:rel='#head.effects' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    8889]>
    8990<?rfc toc="yes" ?>
     
    10361037<t>
    10371038   The response to a HEAD request is cacheable and &MAY; be used to satisfy
    1038    a subsequent HEAD request; see &caching;. It also &MAY; be used to update a previously cached
    1039    representation from that resource; if the new field values
    1040    indicate that the cached representation differs from the current representation (as
    1041    would be indicated by a change in Content-Length, ETag
    1042    or Last-Modified), then the cache &MUST; treat the cache entry as
    1043    stale.
     1039   a subsequent HEAD request. It also has potential side effects on
     1040   previously stored responses to GET; see &p6-head;.
    10441041</t>
    10451042<t>
Note: See TracChangeset for help on using the changeset viewer.