#16676 [WFx->]: ob_implicit_flush not turning off ob
| From: | yohgaki@php.net | Date: | Sat, 11 Jan 2003 23:08:46 +0000 |
| Subject: | #16676 [WFx->]: ob_implicit_flush not turning off ob | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-29799@lists.php.net to get a copy of this message | ||
ID: 16676
Updated by: yohgaki@php.net
Reported By: norny@yahoo.com
Status: Won\'t fix
Bug Type: Output Control
Operating System: Slackware 8.0
PHP Version: 4.2.0
New Comment:
And don't forget that some buffers should never be deleted once it's
started. The error message is raised, since some users don't know it
shouldn't.
Previous Comments:
------------------------------------------------------------------------
[2003-01-11 17:05:17] yohgaki@php.net
Since current output buffer is statelss even if some buffers need
stateful handling to prevent crashes/malformed output/ etc.
Don't start buffer if you don't need it. Complain people who insisted
this behavior. Search php-dev archive ;)
------------------------------------------------------------------------
[2003-01-10 12:32:43] norny@yahoo.com
Now I'm getting a PHP notice in Windows XP using PHP 4.3.0 from the cmd
line.
PHP Notice: ob_end_flush() [<a
href='http://www.php.net/ref.outcontrol'>ref.outcontrol</a>]:
failed to
delete buffer default output handler. in C:\Apache\cgi-bin\mybot.php on
line 58
In previous versions, ob_end_flush was my workaround to
ob_implicit_flush not working. In 4.3.0 ob_end_flush isn't working for
me and it does work in 4.2.3. Could someone make at least one of the
two work again instead of keeping the "Won't fix" status?
------------------------------------------------------------------------
[2002-12-27 08:35:57] yohgaki@php.net
Should have been won't fix
------------------------------------------------------------------------
[2002-12-27 08:16:53] yohgaki@php.net
It is easy to make it actually flush output. Difficult part is make it
work always.
Some output buffers shouldn't be deleted and cannot be deleted. i.e.
Some browsers will freeze if server send malformed compressed output.
Thus ob_end_flush() wouldn't and shouldn't work in some cases. If it
works, it's a bug should be fixed.
Fix is simple, but you have to live with that.
If you are interested, search php-dev archive.
BTW, ob_implicit_flush() simply enable SAPI level auto flushing even if
its name imply PHP output buffer flushing. Don't blame me, I'm for
fixing it ;)
------------------------------------------------------------------------
[2002-12-24 21:39:37] edink@php.net
You can solve your problem by putting @ob_end_flush(); on top of your
command line scripts.
------------------------------------------------------------------------
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/16676
--
Edit this bug report at http://bugs.php.net/?id=16676&edit=1