#23679 [Opn->Bgs]: PHP does not protect output buffers created in configs from the script

ID: 23679 Updated by: helly@php.net Reported By: ngaugler at ngworld dot net -Status: Open +Status: Bogus Bug Type: Output Control Operating System: FreeBSD PHP Version: 4.3.1 New Comment: Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php If you want to shoot your self in the knee go ahead. Previous Comments: ------------------------------------------------------------------------ [2003-05-18 06:51:27] ngaugler at ngworld dot net I do not want PHP to delete the buffers. Let me try and re-explain it. When I setup the ob_gzhandler, then I run ob_clean or ob_clean_flush PHP will send a partially gzip'ed page to the browser or inconsistant results and the page will not display properly. What I am suggesting is that if someone sets ob_gzhandler in the PHP.ini, or a situation like this, they cannot clear it out through the script. It is protected. ------------------------------------------------------------------------ [2003-05-18 05:46:59] helly@php.net Try this: // delete as much output buffers as possible while(@ob_end_clean()); ------------------------------------------------------------------------ [2003-05-18 04:40:49] ngaugler at ngworld dot net PHP does not protect output_buffers created via configs through the output_buffer, output_handler configurations from individual scripts. If you configure your php.ini to have output_handler = ob_gzhandler then run ob_clean() or ob_end_clean() odd results happen and the page does not properly send. I think PHP should protect buffers created before the script is executed so that the individual may not destroy them. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=23679&edit=1