Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1256325

Summary: [GSS](6.4.z) Welcome file does not work for *.jsf
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Kunjan Rathod <krathod>
Component: WebAssignee: Dmitrii Tikhomirov <dtikhomi>
Status: CLOSED CURRENTRELEASE QA Contact: Radim Hatlapatka <rhatlapa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4.2CC: bbaranow, bmaxwell, cdewolf, dpospisi, dtikhomi, fnasser, istudens, jason.greene, jtruhlar, mcada, rhatlapa, rmaucher, rmody, rsvoboda
Target Milestone: CR1   
Target Release: EAP 6.4.7   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 11:56:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1279552, 1308845    
Attachments:
Description Flags
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) none

Description Kunjan Rathod 2015-08-24 11:19:56 UTC
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.

Comment 10 Rostislav Svoboda 2015-10-21 12:23:25 UTC
Changing to proper component.

Comment 30 Brad Maxwell 2016-01-04 22:57:36 UTC
Created attachment 1111569 [details]
tests.zip

Comment 33 Brad Maxwell 2016-01-05 22:24:10 UTC
Created attachment 1111962 [details]
tests.zip

Comment 48 Michael Cada 2016-03-02 12:24:17 UTC
Verified on EAP 6.4.7.CP.CR2

Property org.apache.tomcat.util.http.mapper.STRICT_WELCOME_FILES has to be set to true.

Comment 50 Petr Penicka 2017-01-17 11:56:34 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.