Antwort: Re: Antwort: [Mod_gzip] Issues with 1.3.26.1a: TIFF corrupted (if excluded) and 'Go Back' broken on Win98

[mod_gzip@lists.over.net]

Hi Keith,


>> > (if I excluded the type, the image was getting corrupted somehow)
>> I cannot believe your statement.
> The "corrupted" part, or the fact that excluding image/tiff 'broke'
> the page and including it made it 'work' ?
> I replaced all my rules with a simple  "mod_gzip_item_include
> uri \.p?html?$" (as per somebody's suggestion), and it seemed
> to solve the TIFF problem.

Did you try using the current CVS version of the source code?
It seems that Christian Kruse has fixed a bug related to the
creation of the "Vary:" headers in combination with "exclude"
rules after 1.3.26.1a had been released.

> If you'd like me to do some further tests, I'd be happy to.

As an alternative, you might try to replace excluding a file type
by turning off mod_gzip for this file type, such as

     <Files *.tiff>
     mod_gzip_on no
     </Files>

In this case, mod_gzip will not even be invoked for these files
and will definitely not try to send any "Vary:" header or do
anything else with this file's content.


>> And you should note that 1.3.19.1a is _not_ working correctly in this
>> area - there is a reason for the changes we made, and you have to use
>> the new configurations directives (that weren't even available in
>> 1.3.19.1a) very thoroughly.
> Is there a sample configuration somewhere, please?

It is part of the mod_gzip download package ... or you can find
it at
     http://www.schroepl.net/projekte/mod_gzip/config.htm

>> > 2) Worse than this, certain PCs running IE on Win98 started to give
'page
>> > has expired' when clicking on a 'Go Back' button.
>> Which HTTP method did the previous page (the one you wanted to go
>> "back" to) use, GET or POST?
>> And which HTTP methods did you configure to be gzipped?
> This problem still persists.  It was a POST page.  I tried with my
> new one-liner 'include' configuration and it still did this. What now?

Turn off mod_gzip for either this URL or the whole POST method.

mod_gzip 1.3.26.1a has a directive for doing so:
     http://www.schroepl.net/projekte/mod_gzip/config.htm#requirements

Apache itself would be able to do the same with
     <Limit POST>
     mod_gzip_on no
     </Limit>

Regards, Michael