Ignore:
Timestamp:
Jan 10, 2013, 10:27:20 PM (7 years ago)
Author:
fielding@…
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2107 r2108  
    39003900</artwork><postamble>indicates that the origin server might have used the
    39013901   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 this
    3903    <x:ref>selected representation</x:ref>.
     3902   fields (or lack thereof) as determining factors while choosing the content
     3903   for this response.
    39043904</postamble></figure>
    39053905<t>
     
    39313931   other than the method and request target, unless the variance cannot be
    39323932   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 because
    3935    reuse across users is constrained by the field definition. Likewise,
    3936    Cache-Control directives (&header-cache-control;) might be used to supplant
    3937    the need for Vary, particularly when the variance is considered less
    3938    significant than the performance cost of Vary's impact 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.
    39393939</t>
    39403940</section>
Note: See TracChangeset for help on using the changeset viewer.