Bug #14474 Updated: Apache PHP Module cannot seem to handle large amounts of output
| From: | tonalgeek at hotmail dot com | Date: | Wed, 06 Feb 2002 05:51:18 +0000 |
| Subject: | Bug #14474 Updated: Apache PHP Module cannot seem to handle large amounts of output | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-79312@lists.php.net to get a copy of this message | ||
ID: 14474
Updated by: tonalgeek@hotmail.com
-Reported By: php@brentc.com
+Reported By: tonalgeek@hotmail.com
Status: Critical
Bug Type: Scripting Engine problem
Operating System: Windows XP Pro/Linux
PHP Version: 4.1.0
New Comment:
Adding to my previous comment, I saw no:
<CR>
0
<CR>
<Disconnect>
at the end of my http session.
OK - The HTTP Request is not closed properly. Only got:
blahblah blah blah<br>
<CR>
blafjaskasdjadsjf<font size="1"$sample_write[$i]
<Disconnect>
There must be an <CR>0<CR> at the end of the reply.
Previous Comments:
------------------------------------------------------------------------
[2002-02-05 04:36:55] tonalgeek@hotmail.com
I've used a packet logger and have found that PHP seems to halt
transmission around a php instruction.
The socket is actually closed, I'm not sure if there needs to be an
'END' string at the end of an http session, but there are no CR's or
anything like that on the end.
------------------------------------------------------------------------
[2002-02-05 04:36:45] tonalgeek@hotmail.com
I've used a packet logger and have found that PHP seems to halt
transmission around a php instruction.
The socket is actually closed, I'm not sure if there needs to be an
'END' string at the end of an http session, but there are no CR's or
anything like that on the end.
------------------------------------------------------------------------
[2002-01-18 10:54:20] mcq@email.ro
I've tried the script on PHP 4.0.6, Windows 2000 Pro, Apache 1.3.22,
php installed as a module.
If I use a download manager to access the script it works.
I use Mass Downloader 2.2 and to get the file I write something like
this to the url address: http://localhost/bug.php.
The program starts downloading the file and after downloading 28.55 Mb
stops, but it doesn't say that the download finished and after 5 sec.
it starts downloading the file again. If I set the for loop only to 100
the result is the same, after the program transfers 2.5 Kb it waits for
5 sec. after he tryes again to download it.
But if I try this with IE (when the loop is set to 100) everything it's
ok.
So, after running this tests, I think that the problem is not that PHP
does not support large outputs, but the browser. (28.55 Mb it's a huge
html file).
I've tested IE with the loop set to 100000 and it works.
If I set the loop to 1000000 then I ran aout of memory, because my page
file is only of 380 Mb. But maybe if I would have more memory
everything would be OK.
------------------------------------------------------------------------
[2001-12-15 22:21:55] yohgaki@php.net
Probably, Zeev is right about regarding
[2001-12-12 20:33:45] yohgaki@php.net
update. Since I didn't see active httpd process.
httpd should close connection when PHP cannot execute script, anyway
;)
(I suppose httpd is not closing connection. With my IE under w2k,
networks may become ususable. Mozilla under linux halts. This is
critical :)
More detailed analysys is required. Any volanteers?
------------------------------------------------------------------------
[2001-12-15 11:20:23] zeev@php.net
I don't think that our current analysis is correct. Take a look at the
access log - I'm pretty sure you'd see that the page is being
repeatedly requested by IE, and not requested only once.
Something about the way the server disconnects may cause IE to think
that the page was not properly fetched, and make it try to reload it.
That would be my guess...
------------------------------------------------------------------------
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/14474
--
Edit this bug report at http://bugs.php.net/?id=14474&edit=1