[
https://issues.apache.org/struts/browse/WW-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46242#action_46242
]
Eric Nelson commented on WW-2163:
---------------------------------
Adding this to the default behavior was a bad idea. This just bit us in the
butt. We have urls such as http://www.fake.com/download which is mapped by a
servlet to a JSP. After upgrading to the newer version of Struts2 with this
change, all of our urls stopped working because Struts thought this was a valid
action by default, and redirected to login since my default interceptor is for
authenticated pages. This should be removed as a default setting and anyone
who needs it can explicitly set it in their own struts.properties or struts.xml
file. This caused me a few hours of headache, and I'm sure it'll get others
too.
> Support actions with no extensions, including directory urls
> ------------------------------------------------------------
>
> Key: WW-2163
> URL: https://issues.apache.org/struts/browse/WW-2163
> Project: Struts 2
> Issue Type: Improvement
> Components: Dispatch Filter
> Affects Versions: 2.0.9
> Reporter: Don Brown
> Assignee: Don Brown
> Fix For: 2.1.0
>
>
> Currently, you cannot really expose your actions without using an extension
> via the 'struts.action.extension' setting. If you set it to an empty string,
> Struts will try to handle every URL as an action, not only blocking webapp
> static resources but also its internally served static resources.
> Furthermore, you cannot define an action that will respond to a directory url
> (http://foo.com/myapp/dir/), without using a workaround like a redirection
> jsp page.
> This improvement would allow actions to be accessed without an extension, but
> still allow static resources and other extensions. In otherwords, the death
> of the ".action" extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
