Changeset 2108 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 11/01/13 06:27:20 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r2107 r2108 3900 3900 </artwork><postamble>indicates that the origin server might have used the 3901 3901 request's <x:ref>Accept-Encoding</x:ref> and <x:ref>Accept-Language</x:ref> 3902 fields (or lack thereof) as determining factors while choosing th is3903 <x:ref>selected representation</x:ref>.3902 fields (or lack thereof) as determining factors while choosing the content 3903 for this response. 3904 3904 </postamble></figure> 3905 3905 <t> … … 3931 3931 other than the method and request target, unless the variance cannot be 3932 3932 crossed or the origin server has been deliberately configured to prevent 3933 cache transparency. For example, there is no need to send the 3934 Authorization field name (&header-authorization;) in Vary because3935 reuse across users is constrained by the field definition. Likewise,3936 Cache-Control directives (&header-cache-control;) might be used to supplant3937 the need for Vary, particularly when the variance is considered less3938 significant than the performance cost of Vary'simpact on caching.3933 cache transparency. For example, there is no need to send the Authorization 3934 field name in Vary because reuse across users is constrained by the field 3935 definition (&header-authorization;). Likewise, an origin server might use 3936 Cache-Control directives (&header-cache-control;) to supplant Vary if it 3937 considers the variance less significant than the performance cost of Vary's 3938 impact on caching. 3939 3939 </t> 3940 3940 </section>
Note: See TracChangeset
for help on using the changeset viewer.