We have several CGI scripts which can take over 30 minutes to complete. Usually, the scripts are dumping data to the browser, however there are times where we see a 5 - 10 minute "dead time" where no data is being sent. This is normal. The problem is that Mozilla is giving a timeout after about 2 minutes of idle time. a simple test case would be: ---- #!/usr/bin/perl $|=1; #autoflush the data sent to the browser print "content-type: text/plain\n\n"; print "sleeping for 600 seconds (10 minutes)\n"; sleep 600; print "Done\n"; -----

do other browsers handle this ok? we do intentionally set a timeout in an effort to detect stale connections. sounds like our timeout may be too short.

*** Bug 80717 has been marked as a duplicate of this bug. ***

From dupe 80717: ------- Additional Comments From R.K.Aa 2001-05-14 09:38 ------- sounds like what i see in bug 35844. The sockets time out long before content is served.

Yes, other browsers (IE and Netscape 4.7 and lynx) handle this correctly. Additionally, on the suggested testcase below, you need to modify the webserver timeout to be about 20 minutes, and run the script as a CGI program.

-->darin

reporter: please try this against a recent nightly build. i suspect that it may no longer be a problem.

moving to 0.9.3 to get it off the 0.9.2 radar (though i believe it is fixed).

i believe this was fixed with the http branch landing. marking FIXED.