ID: 20800
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Bogus
+Status: Open
Bug Type: Output Control
Operating System: Redhat 7.0
PHP Version: 4.3.0RC2
New Comment:
I can't do:
ini_set("output_buffering", 0);
output_buffering isn't "PHP_INI_ALL" but is
"PHP_INI_PERDIR|PHP_INI_SYSTEM". I cannot change it in scripts.
Previous Comments:
------------------------------------------------------------------------
[2002-12-30 14:17:31] [EMAIL PROTECTED]
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
to disable output buffering from inside the script simply do:
ini_set("output_buffering", 0);
The reason you do not see an error is same reason that prevents you
seeing the 'a' that you are trying to print.
------------------------------------------------------------------------
[2002-12-11 15:19:25] [EMAIL PROTECTED]
But in "Bug #20642" [EMAIL PROTECTED] suggests this solution to disable
output buffering on a script base.
BTW Why no fatal error is shown?
How can I disable output buffering in a script?
------------------------------------------------------------------------
[2002-12-04 14:40:46] [EMAIL PROTECTED]
As discussed in the past, this behaviour is supposed to be expected. Do
not use ob_end_flush() without preceding ob_start() when gzip output
handler is enabled.
------------------------------------------------------------------------
[2002-12-04 12:53:49] [EMAIL PROTECTED]
I just assumed you meant segfaults by the word "crash" :-)
Okay, Verified in HEAD, both with apache and with apache2.
------------------------------------------------------------------------
[2002-12-04 05:01:10] [EMAIL PROTECTED]
The server doesn't create any core dump, it simply exit, as in bug
#20802, there is no segmentation fault.
------------------------------------------------------------------------
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/20800
--
Edit this bug report at http://bugs.php.net/?id=20800&edit=1
