[Mod_gzip] SEND_AS_IS:HAS_CE message

[Jack Wang]

Hi Kevin,

Thanks for your kind and immediate reply.  I  have understood the term
"Contern-encoding". Thanks.

According to your direction,  I have check php.ini file, but I still cannot
find any setup directives / parameter which have any relation with
"Contern-encoding" in php.ini file.

Could you mind showing me how to find this problem ?  Major directives /
parameters in php.ini are as follows,
.
.
.
output_buffering = 4096
output_handler = ob_gzhandler
zlib.output_compression = Off
..
.
.
[Zend]
zend_optimizer.optimization_level=1023
zend_extension="/usr/local/Zend/lib/ZendOptimizer.so"
zend_loader.enable=Off


PS: I have enabled Zend Opertmizer.
.
Regards,

Jack Wang
----- Original Message -----
From: <TOKILEY@aol.com>
To: <mod_gzip@lists.over.net>
Cc: <jack@zhc.us>
Sent: Friday, May 02, 2003 2:08 PM
Subject: Re: [Mod_gzip] SEND_AS_IS:HAS_CE message


>
> Hello Jack...
>
> SEND_AS_IS:HAS_CE is a very simple response condition.
>
> It means that the response coming back through Apache
> ( from the PHP CGI stuff ) already has some form of
> 'Content-encoding:' and since modern browsers still
> cannot ever handle more than 1 'Content-encoding'
> applied to a response then you can't compress a
> response that ALREADY had a 'Content-encoding'
> applied to it. You have to forward the response 'as-is'
> which is exactly what mod_gzip is doing ( SEND_AS_IS ).
>
> The fact that no browser can deal with 'multiple encodings'
> on the same response means that none of them are
> anywhere near RFC or HTTP/1.1 compliant but that's
> another long story. Any HTTP/1.1 compliant user agent
> is SUPPOSED to be able to 'decode' any number of
> multiple 'Content-encodings:' applied to the same
> response... but none of them actually can do this.
>
> More than likely, the response coming back from
> PHP already has "Content-encoding: gzip" since
> that's about the only 'Content-encoding:' that makes
> any sense according to RFCs. 'gzip' or 'deflate' are
> the only 2 'officially' supported Content encodings
> as per the W3C ( World Wide Web Consortium ).
>
> Check and see what your PHP CGI stuff is actually
> sending. I will bet it already has "Content-encoding: gzip"
> on it. If that's the case... then what's the problem? You
> are already getting what you seem to be asking for.
>
> Yours...
> Kevin
>
>