Re^2: CGI, fork, long processes on Apache 2

I'm not really sure about this, but does your script close STDOUT and STDERR (and possibly repoen them to /dev/null) after the redirect is printed out? This will tell the browser to see a closed connection and it won't wait for anything more.

Comment on Re^2: CGI, fork, long processes on Apache 2

Replies are listed 'Best First'.
Re: Re^2: CGI, fork, long processes on Apache 2 by Vautrin (Hermit) on Apr 04, 2004 at 20:20 UTC
There is a bug in Apache 2.0.x. If you have a long running CGI script you'll see an error in your CGI logs: `The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed`. This is why his script works properly under apache 1.3 and not 2.0.x -- because under Apache 2.0.x there comes a point where it just won't die. Want to support the EFF and FSF by buying cool stuff? Click here.	[reply] [d/l]

Replies are listed 'Best First'.

Re: Re^2: CGI, fork, long processes on Apache 2
by Vautrin (Hermit) on Apr 04, 2004 at 20:20 UTC

The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed

Want to support the EFF and FSF by buying cool stuff? Click here.

[reply]
[d/l]