Oh yes!. AFAIK Squid currently just doesn't cache responses with Vary
headers. The original questions IIRC was is it the "origin servers
responsibility to send a Vary header" or "the caches responsbility to
automagically realise the response was based on User-Agent
information..."
And the coin falls on the origin server :]
Rob
> -----Original Message-----
> From: Dancer Vesperman [mailto:dancer@zeor.simegen.com]
> Sent: Thursday, 16 November 2000 1:58 PM
> To: Robert Collins
> Cc: Adrian Chadd; squid-dev@squid-cache.org
> Subject: Re: [mcmanus@appliedtheory.com: Re: Different web pages for
> different browser versions]
>
>
> (My caps below. I just want to highlight a couple of words)
>
> Robert Collins wrote:
>
> > 13.6
> > ==
> > <!--StartFragment-->
> > A server SHOULD use the Vary header field to inform a
> cache of what
> > request-header fields were used to select among multiple
> > representations of a cacheable response subject to server-driven
> > negotiation. The set of header fields named by the Vary
> field value
> > is known as the "selecting" request-headers.
> >
> > When the cache receives a subsequent request whose Request-URI
> > specifies one or more cache entries including a Vary
> header field,
> > the cache MUST NOT use such a cache entry to construct a
> response to
> > the new request unless all of the selecting
> request-headers present
> > in the new request match the corresponding STORED
> REQUEST-HEADERS in <--
> > the original request.
> > ==
> >
>
>
Received on Wed Nov 15 2000 - 20:02:04 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:12:59 MST