Either we can ignore "struts.token" and "struts.token.name" in the
interceptor or make those params compliant with the regex - rename
them to "struts_token" and "struts_token_name"

niedz., 27 wrz 2020 o 20:00 James Chaplin <jchap...@apache.org> napisaƂ(a):
>
> Hello Greg.
>
> Those log warnings are due to WW-5077 changes (2020/05/24), which are more 
> detailed (and at warn-level) when devMode is true.  When devMode is false, it 
> reverts to the old behaviour of a shorter debug-level-only output.
>
> There is a (fairly old) unit test which indicates "struts.token" and 
> "struts.token.name" are supposed to be excluded by the ParametersInterceptor 
> defaults, so the log warnings would be expected if devMode is true and either 
> of those parameter names are present.
>
> Maybe there should be special logging handling for "struts.token" and 
> "struts.token.name" in the ParametersInterceptor, with devMode true ?  Maybe 
> those two parameters should only produce debug-level log items, to avoid 
> unwanted warnings, with devMode on ?
>
> Regards,
>
> James.
>
> On 2020/09/27 09:24:19, Greg Huber <gregh3...@gmail.com> wrote:
> > WARN  com.opensymphony.xwork2.interceptor.ParametersInterceptor
> > ParametersInterceptor:isExcluded - Parameter [struts.token.name] matches
> > excluded pattern
> > [(^|\%\{)((#?)(top(\.|\['|\[")|\[\d\]\.)?)(dojo|struts|session|request|response|application|servlet(Request|Response|Context)|parameters|context|_memberAccess)(\.|\[).*]!
> > See Accepted / Excluded patterns at

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Reply via email to