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

[jira] [Created] (WW-3880) Silent refusal of parameters without any logging

Tom Briers created WW-3880:
------------------------------

             Summary: Silent refusal of parameters without any logging
                 Key: WW-3880
                 URL: https://issues.apache.org/jira/browse/WW-3880
             Project: Struts 2
          Issue Type: Improvement
          Components: Core Interceptors
    Affects Versions: 2.3.4.1, 2.3.4, 2.3.3, 2.3.1.2
            Reporter: Tom Briers
            Priority: Minor


In version 2.3.4.1 a check on the length of the name has been added in the com.opensymphony.xwork2.interceptor.ParametersInterceptor class.  If the size of the name exceeds the parameter is silently refused without any hint of what happened.

The same problem exists with the other checks to accept a parameter.

Is it possible to add a logging when devMode is active so possible issues can be identified more easily.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (WW-3880) Silent refusal of parameters without any logging

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WW-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464242#comment-13464242 ] 

Hudson commented on WW-3880:
----------------------------

Integrated in Struts2 #534 (See [https://builds.apache.org/job/Struts2/534/])
    WW-3880 adds logging when parameter wasn't accepted (Revision 1390696)

     Result = FAILURE
lukaszlenart : 
Files : 
* /struts/struts2/trunk/xwork-core/src/main/java/com/opensymphony/xwork2/interceptor/ParametersInterceptor.java

                
> Silent refusal of parameters without any logging
> ------------------------------------------------
>
>                 Key: WW-3880
>                 URL: https://issues.apache.org/jira/browse/WW-3880
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Core Interceptors
>    Affects Versions: 2.3.1.2, 2.3.3, 2.3.4, 2.3.4.1
>            Reporter: Tom Briers
>            Assignee: Lukasz Lenart
>            Priority: Minor
>             Fix For: 2.3.5
>
>
> In version 2.3.4.1 a check on the length of the name has been added in the com.opensymphony.xwork2.interceptor.ParametersInterceptor class.  If the size of the name exceeds the set value, the parameter is silently refused without any hint of what happened.
> The same problem exists with the other checks to accept a parameter.
> Is it possible to add a logging when devMode is active so possible issues can be identified more easily.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (WW-3880) Silent refusal of parameters without any logging

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

Lukasz Lenart resolved WW-3880.
-------------------------------

    Resolution: Fixed
      Assignee: Lukasz Lenart

Solved, thanks for reporting!
                
> Silent refusal of parameters without any logging
> ------------------------------------------------
>
>                 Key: WW-3880
>                 URL: https://issues.apache.org/jira/browse/WW-3880
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Core Interceptors
>    Affects Versions: 2.3.1.2, 2.3.3, 2.3.4, 2.3.4.1
>            Reporter: Tom Briers
>            Assignee: Lukasz Lenart
>            Priority: Minor
>             Fix For: 2.3.5
>
>
> In version 2.3.4.1 a check on the length of the name has been added in the com.opensymphony.xwork2.interceptor.ParametersInterceptor class.  If the size of the name exceeds the set value, the parameter is silently refused without any hint of what happened.
> The same problem exists with the other checks to accept a parameter.
> Is it possible to add a logging when devMode is active so possible issues can be identified more easily.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (WW-3880) Silent refusal of parameters without any logging

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

Lukasz Lenart updated WW-3880:
------------------------------

    Fix Version/s: 2.3.5
    
> Silent refusal of parameters without any logging
> ------------------------------------------------
>
>                 Key: WW-3880
>                 URL: https://issues.apache.org/jira/browse/WW-3880
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Core Interceptors
>    Affects Versions: 2.3.1.2, 2.3.3, 2.3.4, 2.3.4.1
>            Reporter: Tom Briers
>            Priority: Minor
>             Fix For: 2.3.5
>
>
> In version 2.3.4.1 a check on the length of the name has been added in the com.opensymphony.xwork2.interceptor.ParametersInterceptor class.  If the size of the name exceeds the set value, the parameter is silently refused without any hint of what happened.
> The same problem exists with the other checks to accept a parameter.
> Is it possible to add a logging when devMode is active so possible issues can be identified more easily.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (WW-3880) Silent refusal of parameters without any logging

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

Tom Briers updated WW-3880:
---------------------------

    Description: 
In version 2.3.4.1 a check on the length of the name has been added in the com.opensymphony.xwork2.interceptor.ParametersInterceptor class.  If the size of the name exceeds the set value, the parameter is silently refused without any hint of what happened.

The same problem exists with the other checks to accept a parameter.

Is it possible to add a logging when devMode is active so possible issues can be identified more easily.

  was:
In version 2.3.4.1 a check on the length of the name has been added in the com.opensymphony.xwork2.interceptor.ParametersInterceptor class.  If the size of the name exceeds the parameter is silently refused without any hint of what happened.

The same problem exists with the other checks to accept a parameter.

Is it possible to add a logging when devMode is active so possible issues can be identified more easily.

    
> Silent refusal of parameters without any logging
> ------------------------------------------------
>
>                 Key: WW-3880
>                 URL: https://issues.apache.org/jira/browse/WW-3880
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Core Interceptors
>    Affects Versions: 2.3.1.2, 2.3.3, 2.3.4, 2.3.4.1
>            Reporter: Tom Briers
>            Priority: Minor
>
> In version 2.3.4.1 a check on the length of the name has been added in the com.opensymphony.xwork2.interceptor.ParametersInterceptor class.  If the size of the name exceeds the set value, the parameter is silently refused without any hint of what happened.
> The same problem exists with the other checks to accept a parameter.
> Is it possible to add a logging when devMode is active so possible issues can be identified more easily.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira