Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

Re: Long CGI process is cut short by browser

by dragonchild (Archbishop)
on Dec 03, 2004 at 14:23 UTC ( [id://412135]=note: print w/replies, xml ) Need Help??


in reply to Long CGI process is cut short by browser

While you have your answer, your question was in error. The browser does not cut off your process - the webserver does. You can also increase the TimeOut parameter to some large number, if needed.

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

  • Comment on Re: Long CGI process is cut short by browser

Replies are listed 'Best First'.
Re^2: Long CGI process is cut short by browser
by Nitrox (Chaplain) on Dec 03, 2004 at 16:28 UTC
    Actually, your reply is in error. Many browsers DO have an internal timeout value. IE's for example defaults to 5mins in v4.x, 60min in v5+, and can be adjusted thru a 'ReceiveTimeout' value in the registry.

    -Nitrox

      I just did a search of my WinXP registry and didn't come across that key. Also, I have set my Apache TimeOut to 15minutes, let it run for 14, and had it work with both IE and Firefox.

      *shrugs*

      Being right, does not endow the right to be rude; politeness costs nothing.
      Being unknowing, is not the same as being stupid.
      Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
      Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

        As mentioned, v5+ has an internal default timeout of 60mins. I suspect you're testing with a newer version of IE?

        Also, that key does not exist in the registry by default, you need to create it if you're looking to adjust the timeout. See this article for more info: http://support.microsoft.com/kb/q181050/

        -Nitrox

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://412135]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others learning in the Monastery: (5)
As of 2024-04-26 07:57 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found