Edit report at http://bugs.php.net/bug.php?id=34071&edit=1
ID: 34071
Comment by: arvenil at klecza dot pl
Reported by: dennis at nocertainty dot com
Summary: buffering is destroyed when using ob_gzhandler and
ob_clean
Status: No Feedback
Type: Bug
Package: Output Control
Operating System: Windows XP SP2
PHP Version: 5CVS-2005-08-10 (dev)
Block user comment: N
Private report: N
New Comment:
You can't change your mind about compression in half way however you can
still kill that buffer and send other.
<?php
ob_start("ob_gzhandler");
echo("trashed");
ob_end_clean();
ob_start("ob_gzhandler");
echo("output");
ob_end_flush();
?>
Previous Comments:
------------------------------------------------------------------------
[2006-01-27 16:32:58] greg at xdissent dot com
this appears to be ob_gzhandler's fault. it seems to send the
content-encoding: gzip header even if ob_end_clean or similar is called
which produces no output. that means that if you use ob_gzhandler and
then change your mind about compression and need to kill that buffer,
you're out of luck. in the following small example, "output" WILL be
printed in plaintext but will be misinterpreted by the browser as
gzipped content.
<?php
ob_start("ob_gzhandler");
echo("trashed");
ob_end_clean();
echo("output");
?>
you can use telnet to better view the situation because it will almost
always result in a white browser window. as others have pointed out,
you have to use the accept-encoding to trigger ob_gzhandler's
compression:
$ telnet localhost 80
GET /ob_test.php HTTP/1.1
Host: localhost
Accept-Encoding: gzip,deflate
now, should ob_gzhandler really be sending the header if the buffer is
ended without outputting anything? should it maybe check the length of
the buffer when it is closed to determine whether or not the
content-encoding header should be sent?
------------------------------------------------------------------------
[2005-08-19 01:00:06] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
------------------------------------------------------------------------
[2005-08-14 23:10:12] dehstil at gmail dot com
I've reproduced the bug. I've been wondering why my script wouldn't run
until I saw this bug. I'm using apache server on win xp with php 4 as a
module.
The above code produced the bug:
<?php
ob_start('ob_gzhandler');
echo 'Should NOT be shown';
ob_clean();
echo 'Should be shown';
?>
With further debuging this doesn't work either:
<?php
function handler($buffer,$mode){
$buffer=ob_gzhandler($buffer,$mode);
return $buffer;
}
ob_start('handler');
echo 'Should NOT be shown';
ob_clean();
echo 'Should be shown';
?>
I noticed that the content-length in my headers was non-zero so I tried
this and lo and behold:
<?php
function handler($buffer,$mode){
$buffer=ob_gzhandler($buffer,$mode);
header('Content-Encoding:');
header('Content-Type: text/plain');
header('Vary:');
return bin2hex($buffer);
}
ob_start('handler');
echo 'Should NOT be shown';
ob_clean();
echo 'Should be shown';
?>
I realized the bug is sending bad gz binary but for some reason the
following code did work...:
<?php
function handler($buffer,$mode){
$buffer=ob_gzhandler($buffer,$mode);
header('Content-Encoding:');
header('Content-Type: text/plain');
header('Vary:');
return gzuncompress($buffer);
}
ob_start('handler');
echo 'Should NOT be shown';
ob_clean();
echo 'Should be shown';
?>
To my surprise, this didn't, thus confusing me:
<?php
function handler($buffer,$mode){
$buffer=ob_gzhandler($buffer,$mode);
header('Content-Encoding:');
header('Content-Type: text/plain');
header('Vary:');
return 'test'.gzuncompress($buffer);
}
ob_start('handler');
echo 'Should NOT be shown';
ob_clean();
echo 'Should be shown';
?>
I'll be looking for the source on cvs and report back to ya!
------------------------------------------------------------------------
[2005-08-11 23:12:45] sni...@php.net
1) Check your php.ini settings (how they differ to whatever you used as
base for your php.ini, -dist or -recommended)
2) Set error_reporting to E_ALL and try again..
------------------------------------------------------------------------
[2005-08-11 20:54:56] dennis at nocertainty dot com
I found someone else who has the same problem as me:
http://www.sitepoint.com/forums/showpost.php?p=2093119&postcount=5
However, I can't find any specific information. I looked through my
Apache error log, and the only thing I found was:
[Wed Aug 10 18:59:56 2005] [error] [client 127.0.0.1] request failed:
erroneous characters after protocol string: \\xff\\xfb\\x1f\\xff\\xfb
\\xff\\xfb\\x18\\xff\\xfb'\\xff\\xfd\\x01\\xff\\xfb\\x03\\xff\\xfd\\x03GET
/gzip2.php HTTP/1.0
[Wed Aug 10 19:00:21 2005] [error] [client 127.0.0.1] request failed:
erroneous characters after protocol string: \\xff\\xfb\\x1f\\xff\\xfb
\\xff\\xfb\\x18\\xff\\xfb'\\xff\\xfd\\x01\\xff\\xfb\\x03\\xff\\xfd\\x03GET
/gzip2.php HTTP/1.0
But I'm not sure if that's entirely relevant. But there's nothing more
that's related to it.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/bug.php?id=34071
--
Edit this bug report at http://bugs.php.net/bug.php?id=34071&edit=1
