Changeset 172 for draft-ietf-httpbis/latest/p6-cache.xml
- Timestamp:
- 23/01/08 02:11:10 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r170 r172 964 964 retransmitting the full response if the cached entry is good, and we 965 965 do not want to pay the overhead of an extra round trip if the cached 966 entry is invalid, the HTTP/1.1 protocolsupports the use of966 entry is invalid, HTTP/1.1 supports the use of 967 967 conditional methods. 968 968 </t> … … 1141 1141 <section title="Non-modifiable Headers" anchor="non-modifiable.headers"> 1142 1142 <t> 1143 Some features of the HTTP/1.1 protocol, such as Digest1143 Some features of HTTP/1.1, such as Digest 1144 1144 Authentication, depend on the value of certain end-to-end headers. A 1145 1145 transparent proxy &SHOULD-NOT; modify an end-to-end header unless the … … 1393 1393 </t> 1394 1394 <t> 1395 There is no way for the HTTP protocolto guarantee that all such1395 There is no way for HTTP to guarantee that all such 1396 1396 cache entries are marked invalid. For example, the request that 1397 1397 caused the change at the origin server might not have gone through … … 1609 1609 the named field or fields, and not to the rest of the request or 1610 1610 response. This mechanism supports extensibility; implementations of 1611 future versions of the HTTP protocolmight apply these directives to1611 future versions of HTTP might apply these directives to 1612 1612 header fields not defined in HTTP/1.1. 1613 1613 </t>
Note: See TracChangeset
for help on using the changeset viewer.