> Typically, you > would want to front a mod_deflate with an HTTP cache, such as mod_cache (or > equivalent). Here mod_cache only makes sense if you have the disk space to > support it, and there is no real one-size-fits-all cache setup.
> This said, our default config is 15 years old, and attempts to disable > deflate for browsers that don't support it, like "Netscape 4". Unless there > are modern browsers that have broken protocol support for transfer encoding, > these obsolete examples need to be removed. These go together a bit Vary, the current workarounds for old browsers cause Vary: User-Agent which is quite a buzzkill for a cache! -- Eric Covener cove...@gmail.com
