[
https://issues.jboss.org/browse/JBAS-9571?page=com.atlassian.jira.plugin....
]
Jim Tyrrell updated JBAS-9571:
------------------------------
Behavior with WildFly 9 seems to be correct. Removed the:
<!--<handlers>
<file name="welcome-content"
path="${jboss.home.dir}/welcome-content"/>
</handlers>—>
Had a few errors at boot, but seemed to echo 404 pages. The content of the 404 page might
need to be productized with the product/project name. Right now it just shows 404 - Not
Found, which is much better than nothing.
Jim Tyrrell
Principal JBoss Solutions Architect
Public Sector Middleware Advocate
720-839-2251 mobile
404 Page Not found Rendering Doesn't Seem to happen
---------------------------------------------------
Key: JBAS-9571
URL:
https://issues.jboss.org/browse/JBAS-9571
Project: Application Server 3 4 5 and 6
Issue Type: Feature Request
Reporter: Jim Tyrrell
Attachments: Screen Shot 2015-07-23 at 8.22.39 AM.png, Screen Shot 2015-07-23 at
8.27.03 AM.png, Screen Shot 2015-07-23 at 8.32.14 AM.png
When running EAP 6.3 and changing the config line from <virtual-server
name="default-host" enable-welcome-root="true"> to
<virtual-server name="default-host" enable-welcome-root="false">
404 errors are generated but the rendered page has zero content. This manifested itself
in OpenShift V3 and it is really hard to know if you server is up and running since no
content is shown even a 404 error message when going to the root context, or any URL as
shown in the screen shots.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)