Issue was closed with the recommendation to use the suppress-stack-trace plugin. I will proceed with this plugin.
On Saturday, June 3, 2017 at 12:50:58 AM UTC-5, Oleg Nenashev wrote: > > Which issue do you mean? > https://issues.jenkins-ci.org/browse/JENKINS-17782 is already marked as > "Fixed". If something needs to be done in the core, maybe it deserves a new > issue. > > пятница, 2 июня 2017 г., 22:20:12 UTC+2 пользователь [email protected] > написал: >> >> Looks like this was logged as an issue: >> https://github.com/jenkinsci/jenkins/pull/765 >> > >> >> On Friday, June 2, 2017 at 12:26:58 PM UTC-5, [email protected] wrote: >>> >>> I'd like to suppress the Stacktrace from the Jenkins error page to avoid >>> unnecessarily leaking information. I can think of three ways to do this. >>> >>> >>> 1. Use the suppress-stack-trace-plugin >>> <https://github.com/jenkinsci/suppress-stack-trace-plugin> which >>> creates a servlet filter to inject a custom error page >>> 2. Serve a custom error page from a reverse proxy when */oops* is >>> requested. >>> 3. Submit PR to allow suppressing the Stacktrace via configuration >>> >>> >>> Does anyone have any insight that could be helpful to me? >>> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1cad4a49-70e0-4f52-83b5-0dcc0523aa40%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
