Re: [jetty-users] Omit Stacktraces in error pages

An example of a web app binding ... https://github.com/jetty-project/jetty-webapp-logging/blob/master/jetty-webapp-logging/src/main/java/org/eclipse/jetty/webapp/logging/CentralizedWebAppLoggingBinding.java And the XML to hook it up ...

Re: [jetty-users] Omit Stacktraces in error pages

Am 30.06.2022 um 06:18 schrieb Greg Wilkins: You can use a GlobalWebappConfigBinding in the deployer to apply an XML file to every deployed context. This should allow you to get the error page and then set the no stack field. Thanks for mentioning all the options and I've used yours to get

Re: [jetty-users] Omit Stacktraces in error pages

Lothar, You can use a GlobalWebappConfigBinding in the deployer to apply an XML file to every deployed context. This should allow you to get the error page and then set the no stack

Re: [jetty-users] Omit Stacktraces in error pages

The server level ErrorHandler is a good place to start. But as you discovered, each WebAppContext also has its own ErrorPageErrorHandler. That means each WebAppContext would need a configuration (in XML works!) to turn off the display of stacks. Another option is to not use the ErrorHandler

[jetty-users] Omit Stacktraces in error pages

Hi, I'm wondering how to get Jetty to omit stack traces in error pages globally (programmatically). I've tried to get the Server's ErrorHandler before start up, after startup and by setting my own in order to set showStack(false). But this has no effect #on added web applications where own