Changeset 1163 for draft-ietf-httpbis/latest/p6-cache.xml
- Timestamp:
- 11/03/11 06:45:30 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r1145 r1163 522 522 <t>the request method associated with the stored response allows it to 523 523 be used for the presented request, and</t> 524 <t>selecting request-header fields nominated by the stored response (if any)524 <t>selecting header fields nominated by the stored response (if any) 525 525 match those presented (see <xref target="caching.negotiated.responses" 526 526 />), and</t> … … 690 690 <section anchor="age.calculations" title="Calculating Age"> 691 691 <t> 692 HTTP/1.1 uses the Age response-header field to convey the estimated age of the692 HTTP/1.1 uses the Age header field to convey the estimated age of the 693 693 response message when obtained from a cache. The Age field value is the 694 694 cache's estimate of the amount of time since the response was generated or … … 940 940 When a cache receives a request that can be satisfied by a stored response 941 941 that has a Vary header field (<xref target="header.vary"/>), it &MUST-NOT; 942 use that response unless all of the selecting request-header fields nominated by942 use that response unless all of the selecting header fields nominated by 943 943 the Vary header field match in both the original request (i.e., that associated 944 944 with the stored response), and the presented request. 945 945 </t> 946 946 <t> 947 The selecting request-header fields from two requests are defined to match if and947 The selecting header fields from two requests are defined to match if and 948 948 only if those in the first request can be transformed to those in the 949 949 second request by applying any of the following: … … 953 953 </t> 954 954 <t> 955 combining multiple message-header fields with the same field name955 combining multiple header fields with the same field name 956 956 (see &header-fields;) 957 957 </t> … … 975 975 </t> 976 976 <t> 977 The stored response with matching selecting request-header fields is known as the977 The stored response with matching selecting header fields is known as the 978 978 selected response. 979 979 </t> … … 1040 1040 <x:anchor-alias value="age-value"/> 1041 1041 <t> 1042 The "Age" response-header field conveys the sender's estimate of the amount1042 The "Age" header field conveys the sender's estimate of the amount 1043 1043 of time since the response was generated or successfully validated at the 1044 1044 origin server. Age values are calculated as specified in <xref … … 1081 1081 <x:anchor-alias value="cache-response-directive"/> 1082 1082 <t> 1083 The "Cache-Control" general-header field is used to specify directives for1083 The "Cache-Control" header field is used to specify directives for 1084 1084 caches along the request/response chain. Such cache directives are 1085 1085 unidirectional in that the presence of a directive in a request does not … … 1506 1506 <x:anchor-alias value="pragma-directive"/> 1507 1507 <t> 1508 The "Pragma" general-header field is used to include1508 The "Pragma" header field is used to include 1509 1509 implementation-specific directives that might apply to any recipient along 1510 1510 the request/response chain. All pragma directives specify optional behavior … … 1532 1532 <t> 1533 1533 <x:h>Note:</x:h> Because the meaning of "Pragma: no-cache" as a 1534 response-header field is not actually specified, it does not provide a1534 header field is not actually specified, it does not provide a 1535 1535 reliable replacement for "Cache-Control: no-cache" in a response. 1536 1536 </t> … … 1548 1548 <x:anchor-alias value="Vary-v"/> 1549 1549 <t> 1550 The "Vary" response-header field conveys the set of request-header fields1550 The "Vary" header field conveys the set of header fields 1551 1551 that were used to select the representation. 1552 1552 </t> … … 1569 1569 <t> 1570 1570 The set of header fields named by the Vary field value is known as the 1571 selecting request-header fields.1571 selecting header fields. 1572 1572 </t> 1573 1573 <t> … … 1583 1583 <t> 1584 1584 A Vary field value of "*" signals that unspecified parameters not limited 1585 to the request-header fields (e.g., the network address of the client), play a1585 to the header fields (e.g., the network address of the client), play a 1586 1586 role in the selection of the response representation; therefore, a cache 1587 1587 cannot determine whether this response is appropriate. A proxy &MUST-NOT; … … 1589 1589 </t> 1590 1590 <t> 1591 The field-names given are not limited to the set of standard request-header1591 The field-names given are not limited to the set of standard header 1592 1592 fields defined by this specification. Field names are case-insensitive. 1593 1593 </t> … … 1605 1605 <x:anchor-alias value="warn-text"/> 1606 1606 <t> 1607 The "Warning" general-header field is used to carry additional information1607 The "Warning" header field is used to carry additional information 1608 1608 about the status or transformation of a message that might not be reflected 1609 1609 in the message. This information is typically used to warn about possible
Note: See TracChangeset
for help on using the changeset viewer.