I'm down to two issues: BROKEN WELCOME-FILE
WebSphere 6.1.0.19 fails to return the welcome-file from the web.xml when presented with the root URL http://myServer/myContext/ of the project. Instead, the request falls through to the Struts2 filter which returns a 404: Error 404: There is no Action mapped for namespace / and action name . BASIC AUTH IS BROKEN All application actions work without security, but after enabling basic auth only the unsecured links work. WebSphere 6.1.0.19 will correctly intercept requests for secured resources, but instead of triggering basic auth, it returns a WebSphere-specific 404 error message, below. The application works flawlessly on Tomcat 5.5 with form-based or basic authentication. Error 404: SRVE0190E: File not found: /secure/MySecureAction.action CUSTOM PROPERTIES The following custom properties are set: com.ibm.ws.webcontainer.assumefiltersuccessonsecurityerror = true com.ibm.ws.webcontainer.invokefilterscompatibility = true Does anybody have any ideas how to fix these problems? There are the security settings in the Web.xml: <security-constraint> <display-name>General User Security Constraint.</display-name> <security-constraint> <display-name>My Security Constraint.</display-name> <web-resource-collection> <web-resource-name>My Secure Stuff</web-resource-name> <url-pattern>/secure/*</url-pattern> <http-method>GET</http-method> <http-method>PUT</http-method> <http-method>HEAD</http-method> <http-method>TRACE</http-method> <http-method>POST</http-method> <http-method>DELETE</http-method> <http-method>OPTIONS</http-method> </web-resource-collection> <auth-constraint> <description>Trusted users.</description> <role-name> MySecurityRole </role-name> </auth-constraint> </security-constraint> <login-config> <auth-method>BASIC</auth-method> </login-config> <security-role> <description>My Security Role</description> <role-name>MySecurityRole</role-name> </security-role> -----Original Message----- From: Struts Two [mailto:struts...@yahoo.ca] Sent: Wednesday, June 03, 2009 10:47 AM To: Struts Users Mailing List Subject: RE: Adding Struts 2.1.6 on WAS 6.1 breaks welcome-file in web.xml > Can you explain why index.html would work and index.jsp would not? I got > <welcome-file>index.html</welcome-file> to work Quite frankly, I do not know. I never had this problem when I was using struts 1. I could do something like this in my welcome file [which would invoke an action instead]: <welcome-file>index.do</welcome> and entering http://<hostname/context worked. However, switching to struts 2, I have had the same problem as yours with http://<hostname/context. Since I found a work-around with the sample index.html, I never bothered to see why, as I had much bigger issues [basic and form based] authentication issues with WAS and struts 2.1.x . I had basic authentication resolved and now working on form-based. I do not see why index.html failed when you enabled security as it just merely redirects to index.jsp to which you have ;otherwise; preferred to go directly. ------------------------------------------------------------------------------ NOTICE: This electronic mail message and any attached files are confidential. The information is exclusively for the use of the individual or entity intended as the recipient. If you are not the intended recipient, any use, copying, printing, reviewing, retention, disclosure, distribution or forwarding of the message or any attached file is not authorized and is strictly prohibited. If you have received this electronic mail message in error, please advise the sender by reply electronic mail immediately and permanently delete the original transmission, any attachments and any copies of this message from your computer system. Thank you. ============================================================================== --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org