Most likely it is the server which is timing out. IIS has at least a couple of timeouts. I'm not an expert on IIS administration, but using the version on my Win2000 workstation, if you look in Internet Services Manager, the first tab on properties for the web server is "Web Site" which has as "Connection Timeout" property (mine is 900 seconds). Then, under the "Home Directory" tab, if you click "Configuration...", there's an "App Options" tab which includes "ASP script timeout" (mine says 90 seconds). I dunno if this applies to CGI scripts. If you are using Perl as an ASP process, you can set the script timeout there using the ScriptTimeout property of the $Server object (I'm guessing that this will still not go any longer than the Connection Timeout, though).
| [reply] |
900 seconds, that's 15 minutes.
I'll try it at 1800 sec.
Thanks,
Wowski
| [reply] |
hmmm ... Are you using CGI.pm? If so, have you checked $CGI::POST_MAX ... it may be set and you'll need to either set it higher or disable it.
| [reply] |
Yes,
I've got $CGI::POST_MAX set to 100Mb.
Wowski
| [reply] |
A related question - can you delay timeout by setting Perl to flush the buffer after every print, and printing a character every x number of chunks? Does the timeout count from the time data was last received from the script, or from the time the script started? | [reply] |