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

[Matt Dickinson]

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


> By the way, has any user tried to _disable_ this check
> (i. e. remove line 5814-5828 from "mod_gzip.c") and made
> any tests with up-to-date browsers?

Yes (it just fixed my problem).

I have just done this (or maybe what I thought to be this) on the mod_gzip.c
version mod_gzip-2.0.40.tar.gz, by commenting lines 2170-2189 out.

The good news, this seems to solve my problem too in the fact that I now get
my .php displayed. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a;
MultiZilla v1.4.0.3H) Gecko/20030312 doesn't seem to have any issue with
this.

The output from the server is now:

HTTP response headers received from server:

[ 15] HTTP/1.0 200 OK
[ 17] Connection: close
[ 35] Date: Tue, 29 Apr 2003 14:12:28 GMT
[ 20] Accept-Ranges: bytes
[ 37] Server: Apache/2.0.40 (Red Hat Linux)
[ 21] Vary: Accept-Encoding
[ 22] Content-Encoding: gzip
[ 20] Content-Length: 6304
[ 43] Content-Type: text/html; charset=ISO-8859-1
      Client-Date: Tue, 29 Apr 2003 14:12:24 GMT
      Client-Response-Num: 1

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 ?


> Regards, Michael

Thanks,

Matt