[Mod_gzip] "mod_gzip_send_vary=Yes" disables caching on IE? (1.3.26.1a)

[Robert Collins]

--=-myfgEU+V9ilwwKWEeMzz
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sat, 2002-12-07 at 12:03, TOKILEY@aol.com wrote:

> Only 3 questions come to mind...
>=20
> 1. Despite what any 'changelog' comment says... how does this
> REALLY work?

When a response is recieved with Vary, an extra code path is called into
play.

It does several things:
1) Compares the Vary: to the cached object(s) matching the URL. If the
Vary: is different, they ALL get ejected from the cache.
2) It creates a master document in the cache that lists all the
variations, or obtains that document if it already exists.
3) The response is added to the master document.
=20
> 2. Has this version of SQUID been released to the public? Last=20
> I heard it has NOT.

Yes, on september 25th. It's squid 2.5 stable 1.

> 3. If it has been released... then how many years will it take before
> this is still not an issue since there is no assurance that anyone
> will 'upgrade' their SQUID just because a new version is out.

That is not something we can fix, and is the same as all the other
broken cache software out there, not just squid < 2.5. However, 2.5 is
seeing lots of use, with all it's new features.

> Also... SQUID 2.5 still does not have full support for ETag
> which means, while finally not trashing all "Vary" requests
> is a step in the right direction ( finally )... it won't mean
> much until there is full ETag support as well.
>=20
> What's the SQUID timeframe on full ETag support
> as per HTTP/1.1 specs?

It's slated for 3.something. We're not sure just yet. Apache's ETAG
support needs serious review first. I did some experimenting, and got
different ETags for the same object (a .gif from the disk). This will
actually interact with full ETag support when it happens in squid to
cause cache misses :[.

There is a DSA development tree that consolidates entities that match on
MD5 within squid, being done by Yee Man Chan. I think that this may end
up being the basis for robust ETag support. Just speculation though.

Rob


--=-myfgEU+V9ilwwKWEeMzz
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA98U1WI5+kQ8LJcoIRAgw9AJ4mv3VtWswvQLY4LfUqImblbu/6cQCeNPN4
ieMmqGseWqctiQ4U/j/ryn0=
=i1o2
-----END PGP SIGNATURE-----

--=-myfgEU+V9ilwwKWEeMzz--