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,


> 1) For some reason, MIME type image/tiff was being messed up by mod_gzip
> unless I did a mod_gzip_include of it.

How did you come to this conclusion?

I doubt very much that mod_gzip will "mess up" any file format, while
it may well be possible that some browser may have problems decompres-
sing gzipped content in certain situations.

So which browser did you use, and did you compare the gzipped output
of the TIFF image (which you will find in your browser's cache) with
the gzipped output of the same image from the previous mod_gzip release?

> (if I excluded the type, the image was getting corrupted somehow)

I cannot believe your statement.

The browsers failure to handle certain content correctly may result
from receicing different HTTP headers, which is definitely the case
between 1.3.19.1a and 1.3.26.1a.

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.

> 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?

Regards, Michael