tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Larry Isaacs <Larry.Isa...@sas.com>
Subject RE: Outstanding bugs before 3.2 final?
Date Fri, 22 Sep 2000 15:11:55 GMT
I'm not sure why this e-mail took so long to arrive.
Hopefully this one won't take as long.

This issue was resolved last night by restoring the
stack traces and adding a ContextManager showStackTraces
attribute that can be set to "false" to turn them off.

Larry

> -----Original Message-----
> From: Larry Isaacs [mailto:Larry.Isaacs@sas.com]
> Sent: Thursday, September 21, 2000 4:02 PM
> To: 'tomcat-dev@jakarta.apache.org'
> Subject: RE: Outstanding bugs before 3.2 final?
> 
> After working with this area of ContextManager, I'm
> not convinced that defining error pages can
> guarantee that the default handler couldn't get
> invoked.  The right exception thrown on top of
> the right exception might unintentionally invoke
> the default handler.
> 
> I haven't tried this, but I think that with
> an error page for java.lang.Throwable and an
> error page for your own special exception
> extending ServletException.  If the error
> page for the special exception threw an
> exception, you would get the default handler.
> 
> I think the only secure way to allow the stack
> traces to remain in the default handler
> is to use a configuration setting that
> can insure they are turned off.
> 
> Larry
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> 

Mime
View raw message