Bug #68859 [Nab]: ob_clean does not clean the buffer.

From:	exsystemchina at gmail dot com	Date:	Mon, 26 Jan 2015 04:08:32 +0000
Subject:	Bug #68859 [Nab]: ob_clean does not clean the buffer.
References:	1	Groups:	php.bugs
Request:	Send a blank email to php-bugs+get-190223@lists.php.net to get a copy of this message

Edit report at https://bugs.php.net/bug.php?id=68859&edit=1 ID: 68859 User updated by: exsystemchina at gmail dot com Reported by: exsystemchina at gmail dot com Summary: ob_clean does not clean the buffer. Status: Not a bug Type: Bug Package: Output Control Operating System: Irrelevant PHP Version: 5.6.4 Block user comment: N Private report: N New Comment: i've got it, ob_* functions operates the SAME buffer configured by output_buffering. Previous Comments: ------------------------------------------------------------------------ [2015-01-26 03:10:11] exsystemchina at gmail dot com so, there's no way for clearing anything of the output at the end of the execution in PHP, despite of setting [out_buffering=off]? ------------------------------------------------------------------------ [2015-01-25 02:28:47] yohgaki@php.net I think you have ouput_buffering = 4096 aren't you? PHP will start to output when buffer size exceeds 4096 bytes. The reason why PHP behaves differently is CLI does NOT enable output_buffering by default. i.e. CLI ignores the setting, since it supposed to be interactive. In conclusion, you have 2 output buffers under web SAPI, but 1 buffer under CLI. That's the reason why. i.e. You aren't cleanup buffer with while(ob_get_level()>1) ------------------------------------------------------------------------ [2015-01-24 11:51:18] exsystemchina at gmail dot com another test case for header processing. using the same test.php, for t.php: <html> <body> AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA  <?php header('Content-Type: text/plain') ?> </body> </html> EXPECTED RESULT: seeing the mime type is text/plain. ACTUALLY: text/html ------------------------------------------------------------------------ [2015-01-20 04:34:22] exsystemchina at gmail dot com Description: ------------ put the 2 test scripts inside the same apache server host directory, and run test.php to see the result. when not setting [out_buffering] with [Off] in php.ini, ob_clean() does not clear the output. But if replace the code marked (*) with those marked (**), everything is okay, Just [HELLO] is output. when setting [out_buffering] with Off, everything is okay. when using php cli, everything is okay. The situation is also found in PHP5.5.9 with apache. Test script: --------------- ====test.php==== <?php //tested under php5.5.9 with apache2.4.7-x64-windows (XAMPP1.8.3) //tested under php5.6.4 with apache2.4.10-x64-kylin-ubuntu-14.04 register_shutdown_function(function() { while (ob_get_level()>1) { ob_end_clean(); } ob_clean(); //........(*) // ob_end_clean(); //......(**) // ob_start(); //......(**) echo ''; echo 'HELLO'; }); ob_start(); while (ob_get_level()>1) { ob_end_clean(); } ob_clean(); //.......(*) //ob_end_clean(); //........(**) //ob_start(); //.......(**) echo ''; require_once 't.php'; ====t.php==== <html> <body>  <?php throw new Exception(); ?> </body> </html> Expected result: ---------------- HELLO Actual result: -------------- <html> <body>  HELLO ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=68859&edit=1