Re^2: Altering data in STDIN

I have only one misunderstanding:
if I have forked off CGI app and it gave it's result to the real STDOUT, how can I stop Apache from moving on through the handler's chain and launching this application again?

return OK; - says to Apache that all is fine and it can move on.
return AUTH_REQUIRED; - says to stop and return 401 to the user.

The rest of the returns:

Apache2::Const::AUTH_REQUIRED
Apache2::Const::DECLINED
Apache2::Const::DONE
Apache2::Const::FORBIDDEN
Apache2::Const::NOT_FOUND
Apache2::Const::OK
Apache2::Const::REDIRECT
Apache2::Const::SERVER_ERROR
[download]

just seem useless.

Comment on Re^2: Altering data in STDIN Select or Download Code

Replies are listed 'Best First'.
Re^3: Altering data in STDIN by RMGir (Prior) on Sep 02, 2008 at 11:18 UTC
I was thinking more in terms of replacing x.cgi with an intermediate script, and having the intermediate fork off and call the real x... Mike	[reply]