Re: [squid-users] Re: Vary header caching problems

Problem confirmed. For some reason the HTTP headers are not known when
the variance is calculated on stored objects.

More results shortly.

--
Henrik
Rick Byers wrote:
> 
> On Tue, 18 Sep 2001, Henrik Nordstrom wrote:
> 
> > Vary support is in the Squid-HEAD so it should work, BUT be warned that
> > many HTTP servers set objects to expire immediately when generating a
> > Vary header.
> > What does the reply headers look like on the Vary:ing object?
> 
> The request from squid (as seen by the "upstream proxy") looks like:
> GET http://XXX.uwaterloo.ca/test.gif HTTP/1.0
> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
> application/vnd.ms-powerpoint, application/vnd.ms-excel,
> application/msword, */*
> Accept-Language: en-ca
> User-Agent: Mozilla/4.0 (compatible; MSIE 6.0b; Windows NT 5.0)
> X-MyHeader: 20,4
> Via: 1.1 YYY.uwaterloo.ca:3128 (Squid/2.5-DEVEL)
> X-Forwarded-For: 129.97.X.Y
> Host: XXX.uwaterloo.ca
> Cache-Control: max-age=259200
> 
> And the response from the upstream proxy (which in my case is actually the
> one that understands the X-MyHeader header and adds the Vary response)
> looks like:
> HTTP/1.0 200 OK
> Connection: close
> Date: Mon, 17 Sep 2001 22:18:57 GMT
> Server: Apache/1.3.20 (Unix) mod_ssl/2.8.4 OpenSSL/0.9.6a
> Last-Modified: Thu, 30 Aug 2001 14:45:20 GMT
> ETag: "1f538e-1f33-3b8e5180"
> Accept-Ranges: bytes
> Content-Type: image/gif
> Vary: X-MyHeader
> 
> Could the ETag be causing a problem?  I could try having the upstream
> proxy remove it.
> 
> Thanks,
>         Rick