Antwort: Re: Antwort: Re: [Mod_gzip] [ANNOUNCEMENT] mod_gzip 1.3 .26.1a

[mod_gzip@lists.over.net]

Hi Rob,


>> Please read
>>      http://www.schroepl.net/projekte/mod_gzip/cache.htm
>> completely and thoroughly, and if this doesn't answer all
>> your questions, then feel free to ask again.
> OK, so the new changes are to handle proxies and caches with Vary
> headers and exclude rules to better serve all browsers :)

exactly.
This will require the proxies to understand what they ought
to do, but previously they didn't even have a chance at all.

So the new release will help new proxies working, and it will
turn old proxies from serving wrong content to not caching it.

>> caching of your pages by writing the proper "exclude" rules.
> Is there a recommended config section for maximizing the effective-
> ness of cached pages? Or a good list of exclude rules that should
> be used? I see many examples, but not sure which ones are the best,
> etc...? Maybe I should read some more :)

The best that we know about configuration is what out documen-
tation will tell you. We don't have some separate section for
performance tuning, as the current situation is such that
a) you will definitely have a trade-off between standards
   compliancy and performance and
b) the 1.3.26.1a release is still sending too many "Vary:"
   headers, as Todd Vierling has already posted as bug on the
   SourceForge site.
But to absolutely minimize the "Vary:" headers would require
- either the user to understand what he/she is doing, and add
  corresponding Apache directives (like "mod_gzip on no" condi-
  tional on some URI file/patterns, using <FilesMatch> etc.)
- or a total rewrite of the current mod_gzip rules evaluation
  procedure. This is _not_ to be done by some simple patch.

> The part that I am unsure of enabling is mod_gzip_can_negotiate,
> as I do not think we will utiltize it...

In general, it is a good rule of thumb to _not_ enable anything
you don't fully understand. ;-)

Regards, Michael