Mailing-List: contact issues-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@struts.apache.org
Date: Tue, 3 Nov 2015 18:38:27 +0000 (UTC)
From: "Pablo Lozano (JIRA)" <jira@apache.org>
To: issues@struts.apache.org
Message-ID: <JIRA.12910095.1446575860000.139943.1446575907738@Atlassian.JIRA>
In-Reply-To: <JIRA.12910095.1446575860000@Atlassian.JIRA>
References: <JIRA.12910095.1446575860000@Atlassian.JIRA>
 <JIRA.12910095.1446575860321@arcas>
Subject: [jira] [Created] (WW-4560) ParametersInterceptor check for valid
 values blocks many acceptable values using the same rules for parameters.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Pablo Lozano created WW-4560:
--------------------------------

             Summary: 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.24, 2.3.20
            Reporter: Pablo Lozano


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)