-
-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a default error page #20
Comments
That is a very good plan. Do you know how to do this? If so; please create a pull request for it. I'll help you through the process if you need help. Otherwise, I'll work on it in some time. Regards, Robert de Bock. |
Hi @pjsharpe07. The role now places a simple, unbranded default page. That should solve your Nessus finding. Please let me know if this works for you. |
Thank you for doing this! Unfortunately, we remove some of those folders so this fix didn't quite work for us. Instead, we did some work with serverinfo.properties. You can find some of the changes here. Thanks again for doing this work! |
Proposed feature
Default error landing page doesn't exist and some tomcat information is sent. Also, the default page exposes sensitive information as well.
See screen shot:
Rationale
A default error page could prevent this potentially sensitive information from being inadvertently disclosed.
Additional context
Found this via a nessus scan.
The text was updated successfully, but these errors were encountered: