[
https://issues.apache.org/jira/browse/WW-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167473#comment-15167473
]
ASF subversion and git services commented on WW-4560:
-----------------------------------------------------
Commit 5efc5950117651b2505f6b2a8f6ccc825d4af86f in struts's branch
refs/heads/support-2-3 from [~lukaszlenart]
[ https://git-wip-us.apache.org/repos/asf?p=struts.git;h=5efc595 ]
WW-4560 Reverts checking if value is excluded and uses Internal Security
Mechanism
> ParametersInterceptor check for valid values blocks many acceptable values
> using the same rules for parameters.
> ---------------------------------------------------------------------------------------------------------------
>
> Key: WW-4560
> URL: https://issues.apache.org/jira/browse/WW-4560
> Project: Struts 2
> Issue Type: Bug
> Components: Core Interceptors
> Affects Versions: 2.3.20, 2.3.24
> Reporter: Pablo Lozano
> Labels: Interceptors, validation
> Fix For: 2.3.25
>
>
> Commit :5ebc0643b55d728a6713a82559a594d875452cd8
> Added an extra check to validate also parameter Values. Before it only
> checked if the parameter is accepted.
> This extra check is not allowing some values to be used as they are being
> blocked which should be perfectly valid values.
> The same rules to validate parameters should not be the same for the values.
> Is there a reason why this is implemented this way?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
