Changeset 888
- Timestamp:
- 23/07/10 14:45:21 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r886 r888 76 76 <!ENTITY p6-heuristic "<xref target='Part6' x:rel='#heuristic.freshness' 77 77 xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 78 <!ENTITY p6-explicit "<xref target='Part6' x:rel='#calculating.freshness.lifetime' 79 xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 80 <!ENTITY p6-combine "<xref target='Part6' x:rel='#combining.headers' 81 xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 78 82 ]> 79 83 <?rfc toc="yes" ?> … … 864 868 </t> 865 869 <t> 866 The response to a GET request is cacheable if and only if it meets867 the requirements for HTTP caching described in &caching;.870 The response to a GET request is cacheable and &MAY; be used to satisfy 871 subsequent GET and HEAD requests (see &caching;). 868 872 </t> 869 873 <t> … … 889 893 </t> 890 894 <t> 891 The response to a HEAD request &MAY; be cacheable in the sense that the892 information contained in the response &MAY; be used to update a893 previously cached representation from that resource. If the new field values895 The response to a HEAD request is cacheable and &MAY; be used to satisfy 896 a subsequent HEAD request; see &caching;. It also &MAY; be used to update a previously cached 897 representation from that resource; if the new field values 894 898 indicate that the cached representation differs from the current representation (as 895 899 would be indicated by a change in Content-Length, Content-MD5, ETag … … 942 946 </t> 943 947 <t> 944 Responses to this method are not cacheable, unless the response 945 includes appropriate Cache-Control or Expires header fields. However, 946 the 303 (See Other) response can be used to direct the user agent to 947 retrieve a cacheable resource. 948 Responses to POST requests are cacheable only when they 949 include explicit freshness information (see &p6-explicit;). Such 950 cached POST responses &MAY; be used to satisfy subsequent GET and 951 HEAD requests. Note that POST caching is not widely implemented. 952 However, the 303 (See Other) response can be used to direct the 953 user agent to retrieve a cacheable resource. 948 954 </t> 949 955 </section> … … 1039 1045 If the request passes through a cache and the Effective Request URI 1040 1046 identifies one or more currently cached representations, those entries &SHOULD; be 1041 treated as stale. Responses to the DELETE method &MUST-NOT; be cached.1047 treated as stale. Responses to the DELETE method are not cacheable. 1042 1048 </t> 1043 1049 </section> … … 1071 1077 "message/http" (see &media-type-message-http;) and contain a message-body 1072 1078 that encloses a copy of the entire request message. 1073 Responses to the TRACE method &MUST-NOT; be cached.1079 Responses to the TRACE method are not cacheable. 1074 1080 </t> 1075 1081 </section>
Note: See TracChangeset
for help on using the changeset viewer.