Evan A. Zacks wrote: > > Attached is a patch to address this problem. I have only tested > it running as a CGI, however. Does anyone know if this is a > reasonable approach to allowing fatalsToBrowser (or another > custom die handler) to pass through? > > The idea is that if a custom handler is installed, the > http_error() method should not generate any output, but should > rethrow the exception.
The patch looks OK to me. If someone really wants to install a global signal handler /AND/ have http_error() display HTML in this case, they can locally disable the signal handle. Still, I'd like a second opinion on the patch. Michael Peters? Mark --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
