Re: 'ob_gzhandler' conflicts with 'zlib output compression'

From: Date: Tue, 27 May 2003 01:18:53 +0000
Subject: Re: 'ob_gzhandler' conflicts with 'zlib output compression'
References: 1  Groups: php.general 
Request: Send a blank email to php-general+get-149025@lists.php.net to get a copy of this message
Guess: zlib output cmpression is being turned on in your php.ini and you're trying to se ob_gzhandler in your ob_start in mainfile.php on line 19, which would basically ask PHP to compress your output twice. From php.ini: ; You can redirect all of the output of your scripts to a function. For ; example, if you set output_handler to "mb_output_handler", character ; encoding will be transparently converted to the specified encoding. ; Setting any output handler automatically turns on output buffering. ; Note: People who wrote portable scripts should not depend on this ini ; directive. Instead, explicitly set the output handler using ob_start(). ; Using this ini directive may cause problems unless you know what script ; is doing. ; Note: You cannot use both "mb_output_handler" with "ob_iconv_handler" ; and you cannot use both "ob_gzhandler" and "zlib.output_compression". ;output_handler = effects on browser: dunno. depends on whether php obeys you without question or tries to cover up your mistake. solution: your output is already being compressed. don't try to do it again in mainfile.php On Monday 26 May 2003 02:24 am, Ronald Wiplinger wrote: > I have upgraded to Apache 2.0.45 and PHP-4.3.2RC2 and find now many lines > in the apache log files: > > [client 192.168.250.117] PHP Warning: ob_start(): output handler > 'ob_gzhandler' conflicts with 'zlib output compression' in > /usr/local/httpd/virtual/e-paper.elmit.com/htdocs/mainfile.php on line 19 > > What have I missed? What does it do to the browser? > > bye > > Ronald

« previous php.general (#149025) next »