Antwort: RE: Antwort: RE: Antwort: RE: [Mod_gzip] Empty output with all .php pages

[mod_gzip@lists.over.net]

Hi Matt,


>> Use "http_trace.pl" to inspect the HTTP headers of your
>> PHP page's output.
>> This will tell you which Content-Encoding is already
>> applied there ... it isn't reasonable to guess what's
>> going on when you have the option to _know_.
> HTTP response headers received from server:
>
> [ 15] HTTP/1.0 200 OK
> [ 17] Connection: close
> [ 35] Date: Tue, 29 Apr 2003 14:10:41 GMT
> [ 20] Accept-Ranges: bytes
> [ 37] Server: Apache/2.0.40 (Red Hat Linux)
> [ 21] Vary: Accept-Encoding
> [ 22] Content-Encoding: gzip
> [ 43] Content-Type: text/html; charset=ISO-8859-1
> Client-Date: Tue, 29 Apr 2003 14:10:37 GMT
> Client-Response-Num: 1
> Client-Transfer-Encoding: chunked

so your output _is_ already compressed anyway?
(_And_ additionally using chunks? This might well
be a little too much for some of the browsers ...)

What do you then expect mod_gzip to do, other than
just telling you about this?

> This seems to say that the content encoding is the same
> for both of the versions. Doesn't this indicate that it
> was wrongly marked as HAS_CE ?

I am not quite sure which one of your HTTP header
sets was created with mod_gzip enabled/disabled.

But if mod_gzip has been turned off and your content
were still being compressed, then "HAS_CE" would be
telling you exactly what happened: mod_gzip didn't
find anything suitable for being compressed.

Regards, Michael