Created attachment 1066322 [details] The jsf-bug-reproducer.zip/jboss-welcome-bug-1.0-SNAPSHOT.war can be used to reproduce the issue in a plain JBoss EAP 6.4.2(latest) Description of problem: welcome files in web.xml don't work for *.jsf Version-Release number of selected component (if applicable): How reproducible: Every Time Steps to Reproduce: 1) deploy a JSF Application with the following in web.xml:- ... <servlet> <servlet-name>Faces Servlet</servlet-name> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>*.jsf</url-pattern> </servlet-mapping> ... <welcome-file-list> <welcome-file>index.jsf</welcome-file> </welcome-file-list> 2) go to /yourcontext/ --> jboss show you a 404 page: JBWEB000065: HTTP Status 404 - /yourcontext/ 3) go to /yourcontext/index.jsf --> it displays the page. Actual results: 404 page: JBWEB000065: HTTP Status 404 Expected results: To display the *.jsf welcome page Additional info: The reproducer is attached. The issue is fixed in WILDFLY 8.1.0 CR1 and FINAL. Workaroud exists:- Yes, create a dummy(and plain or empty) *.jsf (index.jsf for example) inside the war which allows to have the welcome-root as index.jsf and works as expected.
Changing to proper component.
Created attachment 1111569 [details] tests.zip
Created attachment 1111962 [details] tests.zip
Verified on EAP 6.4.7.CP.CR2 Property org.apache.tomcat.util.http.mapper.STRICT_WELCOME_FILES has to be set to true.
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.