You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Don Brown (JIRA)" <ji...@apache.org> on 2007/09/08 09:07:41 UTC

[jira] Created: (WW-2163) Support actions with no extensions, including directory urls

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
    Affects Versions: 2.0.9
            Reporter: 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.


[jira] Resolved: (WW-2163) Support actions with no extensions, including directory urls

Posted by "Don Brown (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/struts/browse/WW-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Don Brown resolved WW-2163.
---------------------------

    Resolution: Fixed
      Assignee: Don Brown

Fixed, and as part of the fix, I changed the default struts.action.extension setting to 'action,,'.  This will allow struts to properly use the <default-action-ref> element in struts.xml to work as expected for the package's namespace.

> 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
>    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.


[jira] Commented: (WW-2163) Support actions with no extensions, including directory urls

Posted by "Eric Nelson (JIRA)" <ji...@apache.org>.
    [ 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.