Re: gzip/squid patch

Mark Swanson <[email protected]>
Newsgroups gmane.network.tux
Organization Web Service Solutions
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On November 16, 2002 02:18 pm, Miles Elam wrote:
>
> Joe Cooper wrote:
> > Squid 2.5.STABLE1 does support Vary headers, and obeys them...so if
> > you send a vary header, older Squids won't cache it, new Squids will
> > cache it correctly.  (I think.  Henrik wrote the code, and Robert
> > spent some time on the mod_gzip/Squid-Dev lists hashing out what
> > happens when.  I can't seem to get any search results from the
> > squid-dev list right now, so I don't have a link to point to---but it
> > is definitely in the archives.)
>
> If this is the case, I think that it would make sense to only specify
> "Vary: Accept-Encoding" when the compression proc variable is non-zero.
>  After all, if the variable is zero, the content encoding never varies,
> right?  I think that is correct behavior.  If you want the header to
> always be sent, you could always turn compression on but never generate
> a *.gz on the filesystem.  This would more accurately represent the
> possibility of varying content without ever actually supplying it.
>
> Patch forthcoming and I'll try to find some web space for it so people
> can have a URL.
>
> Anything I missed or misunderstood?
>
> - Miles

OK. Vary: Accept-Encoding it is.

Based on my experience I believe only specifying the Vary header for 
compression will work properly.

I believe that's it. I'll do some more testing and if no one hears from me 
it's all good.

Cheers.

- -- 
Schedule your world with ScheduleWorld.com
http://www.ScheduleWorld.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE91q5GBtoFHHwdJ/cRAm/2AJ9NM6Ul7EKoYuWzV2SPGH/1AKLmtACfbdAG
/IojG4DcUSnJh52LOzKmp+s=
=JoeK
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.