DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13507>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13507 capturing stderr from mod_cgi Summary: capturing stderr from mod_cgi Product: Apache httpd-2.0 Version: 2.0.42 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: mod_cgi AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] Currently mod_cgi captures all STDERR data and writes it to the error log via log_script_err() or writes it into a report via log_script(). I would like to write an independent 2.0 module, that is able to do "it's own thing" if "stderr" arrives after running mod_cgi(). Either as a special hook that only mod_cgi(d) looks for: if ((ret = ap_scan_script_header_err_brigade(r, bb, sbuf))) { if (ap_has_stderr_hook()) { return do_stderr_hook(r, conf, ret, dbuf, sbuf, bb, script_err); } return log_script(r, conf, ret, dbuf, sbuf, bb, script_err); } Or at a global stage, like the other handlers (though caching the results of stderr could be expensive). TCL throws cgi errors to stderr. Currently we use a hacked up version of mod_cgi for this reason....when a cgierr happens, it escaltes the error to certain people, and generates an HTML based report they can click on via a JavaScript confirm box "A cgi error has occurred. Do you want to see it ?" Phil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
