[
https://issues.apache.org/struts/browse/WW-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Brown resolved WW-2489.
---------------------------
Resolution: Not A Problem
This is by design, as the times you use static parameters is usually when you
need to set the action in a certain state before the parameters are applied.
Now, there is the risk you mention, which is why it is suggested to be very
careful with what methods are called and/or using the ParameterNameAware
interface to have full control over what parameters are set from the request.
> Interceptor Stack Order
> -----------------------
>
> Key: WW-2489
> URL: https://issues.apache.org/struts/browse/WW-2489
> Project: Struts 2
> Issue Type: Bug
> Components: XML Configuration
> Affects Versions: 2.0.11
> Environment: any
> Reporter: Fabio Gandola
> Priority: Minor
>
> struts-default.xml (struts 2.0.11) gives this interceptor order in the stacks:
> <interceptor-ref name="staticParams"/>
> <interceptor-ref name="params"/>
> is it correct that staticParams comes before params ? this allow GET and POST
> variable to overwrite statically set parameters. Maybe this can lead to
> security risks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
