httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dietz, Phil E." <>
Subject RE: ScriptLog
Date Mon, 08 Sep 2003 15:38:56 GMT
If we ever get the cgi-stdout-stdin-stderr read deadlocking issue fixed...

I did some initial work to make mod_cgi allow 3rd party modules to register StderrAndOutput
filters  (techically, ScriptLog is itsself a StderrAndOutput filter and is added as the default).

So you could have a mod_javascript_cgi_debugging module that emits javascript code if stderr
is present.  If they click the javascript alert, it opens a debugging window with your posted
form vars, etc.

The reason it's called StderrAndOutput filter is, depending on data in the stderr, output
may conditionally be good or bad  (you could force a CGI bomb to be a status 200 or a status
500, output an error page, etc.).

-----Original Message-----
From: Manoj Kasichainula []
Sent: Monday, September 08, 2003 3:08 AM
Subject: Re: ScriptLog

On Sun, Sep 07, 2003 at 05:38:56PM -0400, Cliff Woolley wrote:
> On Sun, 7 Sep 2003, Manoj Kasichainula wrote:
> > If it's only for debugging, can't CGI writers just add a line to their
> > code to rebind stderr to a file?
> Only if the error is output from the script as opposed to a compilation
> failure or other interpreter weirdness.

Good point. The other alternative I've pondered is for people
debugging their own CGIs to use a wrapper that rebinds stderr and
execs the original CGI, but I suspect I'll get shouted down at this
point :)

View raw message