[
https://issues.apache.org/jira/browse/WW-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363204#comment-15363204
]
Aleksandr Mashchenko commented on WW-4656:
------------------------------------------
The {{/static/}} is/was different way before 2.5 - see [Static
Content|http://struts.apache.org/docs/static-content.html].
Since 2.5 static resources are loaded first -
https://issues.apache.org/jira/browse/WW-4621, that is why your setup acts
differently after version upgrade.
To redirect unknown request to the home page consider using default action and
[Unknown Handlers|http://struts.apache.org/docs/unknown-handlers.html].
> Wildcard redirect and path /static/
> -----------------------------------
>
> Key: WW-4656
> URL: https://issues.apache.org/jira/browse/WW-4656
> Project: Struts 2
> Issue Type: Bug
> Affects Versions: 2.5, 2.5.1
> Reporter: Markus Fischer
> Priority: Minor
> Fix For: 2.5.2
>
>
> I do stumble over a new behaviour in Struts 2.5.
> Working with:
> {code:xml}
> <action name="*">
> <result type="redirect">
> <param name="location">/home</param>
> <param name="namespace">/</param>
> </result>
> </action>
> {code}
> To catch/redirect unknown request to the home page, the following requests
> will not be processed:
> https://localhost:8443/myApp/static/whatever
> The path /static/ seems to trigger a "special" behaviour since Struts 2.5?
> There is also an inconsistency between:
> https://localhost:8443/myApp/whatever/ (correct 404)
> https://localhost:8443/myApp/static/ (empty white page)
> Why is the path /static/ treated differently, and where is the exact class
> responsible for this?
> Thanks for considering.
> Markus
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
