ID: 11546
Updated by: [EMAIL PROTECTED]
Reported By: btanner at home dot com
-Status: Analyzed
+Status: Bogus
Bug Type: Scripting Engine problem
Operating System: Windows 2000
PHP Version: 4.0.5
New Comment:
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments
to the existing bug instead.
Thank you for your interest in PHP.
See bug #20447
Previous Comments:
------------------------------------------------------------------------
[2002-09-11 11:48:35] Xuefer at 21cn dot com
sorry for my bad version desc
-> php4.2.0 win binary build with apache
should be wrote as: php4.2.0 Win, run as Apache module
------------------------------------------------------------------------
[2002-09-11 11:45:42] Xuefer at 21cn dot com
same problem under php4.2.0 win binary build with apache
the data is exactly sent after flush()
"I have to wait until my shutdown functions are done before I see the
page"
not 100% true, it's ie problem.
ie will only show page after X bytes(unkown to me) of data, or page
finished
the truth is: php/apache still holding connection until
shutdown_functions done
------------------------------------------------------------------------
[2001-06-21 14:05:23] [EMAIL PROTECTED]
I can now reproduce the same symptom.
If PHP is as CGI under Apache, the example script
doesn't work. But as DSO it works.
------------------------------------------------------------------------
[2001-06-19 14:34:50] btanner at home dot com
Windows 2000 - Apache 1.3x
PHP 4.05
Running PHP.exe as CGI. Is this the problem?
------------------------------------------------------------------------
[2001-06-19 14:23:17] [EMAIL PROTECTED]
This works for me just fine within Linux.
Also on Windows ME (PHP as Apache DSO).
What is the SAPI you are using? Web server?
Or is it run as CGI?
--Jani
------------------------------------------------------------------------
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/11546
--
Edit this bug report at http://bugs.php.net/?id=11546&edit=1
