Changeset 1692 for draft-ietf-httpbis/latest/p6-cache.xml
- Timestamp:
- 23/06/12 12:01:38 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r1689 r1692 15 15 <!ENTITY ID-MONTH "June"> 16 16 <!ENTITY ID-YEAR "2012"> 17 <!ENTITY mdash "—"> 18 <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>"> 17 19 <!ENTITY architecture "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 18 20 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 635 637 </t> 636 638 <t> 637 Additionally, clients can influence freshness calculation --either638 constraining it relaxing it --by using the max-age and min-fresh639 Additionally, clients can influence freshness calculation — either 640 constraining it relaxing it — by using the max-age and min-fresh 639 641 request cache directives. See <xref target="cache-request-directive" /> 640 642 for details. … … 694 696 <x:note> 695 697 <t> 696 <x:h>Note:</x:h>RFC 2616 (<xref target="RFC2616" x:fmt=","698 &Note; RFC 2616 (<xref target="RFC2616" x:fmt="," 697 699 x:sec="13.9"/>) required that caches do not calculate heuristic 698 700 freshness for URIs with query components (i.e., those containing '?'). … … 1201 1203 <x:note> 1202 1204 <t> 1203 <x:h>Note:</x:h>HTTP/1.0 caches might not implement Cache-Control and1205 &Note; HTTP/1.0 caches might not implement Cache-Control and 1204 1206 might only implement Pragma: no-cache (see <xref target="header.pragma" 1205 1207 />). … … 1379 1381 fields defined by this specification. Field names are case-insensitive. 1380 1382 </t> 1381 <t> <x:h>Note:</x:h>This usage of the word "private" only controls1383 <t>&Note; This usage of the word "private" only controls 1382 1384 where the response can be stored; it cannot ensure the privacy of the 1383 1385 message content. Also, private response directives with field-names are … … 1408 1410 fields defined by this specification. Field names are case-insensitive. 1409 1411 </t> 1410 <t> <x:h>Note:</x:h>Most HTTP/1.0 caches will not recognize or obey1412 <t>&Note; Most HTTP/1.0 caches will not recognize or obey 1411 1413 this directive. Also, no-cache response directives with field-names are 1412 1414 often handled by implementations as if an unqualified no-cache directive … … 1598 1600 <x:note> 1599 1601 <t> 1600 <x:h>Note:</x:h>If a response includes a Cache-Control field with the1602 &Note; If a response includes a Cache-Control field with the 1601 1603 max-age directive (see <xref target="cache-response-directive" />), 1602 1604 that directive overrides the Expires field. Likewise, the s-maxage … … 1674 1676 <x:note> 1675 1677 <t> 1676 <x:h>Note:</x:h>Because the meaning of "Pragma: no-cache" in responses is not1678 &Note; Because the meaning of "Pragma: no-cache" in responses is not 1677 1679 specified, it does not provide a reliable replacement for 1678 1680 "Cache-Control: no-cache" in them.
Note: See TracChangeset
for help on using the changeset viewer.