Changeset 2108 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

11/01/13 06:27:20 (10 years ago)

Author:

fielding@…

Message:

(editorial) Vary applies to any response content, not just the selected representation

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -3900 +3900 @@
 </artwork><postamble>indicates that the origin server might have used the
    request's <x:ref>Accept-Encoding</x:ref> and <x:ref>Accept-Language</x:ref>
-   fields (or lack thereof) as determining factors while choosing this
-   <x:ref>selected representation</x:ref>.
+   fields (or lack thereof) as determining factors while choosing the content
+   for this response.
 </postamble></figure>
 <t>
@@ -3931 +3931 @@
    other than the method and request target, unless the variance cannot be
    crossed or the origin server has been deliberately configured to prevent
-   cache transparency. For example, there is no need to send the
-   Authorization field name (&header-authorization;) in Vary because
-   reuse across users is constrained by the field definition. Likewise,
-   Cache-Control directives (&header-cache-control;) might be used to supplant
-   the need for Vary, particularly when the variance is considered less
-   significant than the performance cost of Vary's impact on caching.
+   cache transparency. For example, there is no need to send the Authorization
+   field name in Vary because reuse across users is constrained by the field
+   definition (&header-authorization;). Likewise, an origin server might use
+   Cache-Control directives (&header-cache-control;) to supplant Vary if it
+   considers the variance less significant than the performance cost of Vary's
+   impact on caching.
 </t>
 </section>