[ 
https://issues.apache.org/jira/browse/MYFACES-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17986239#comment-17986239
 ] 

Volodymyr Siedlecki commented on MYFACES-4727:
----------------------------------------------

For example `RANDOM_KEY_IN_VIEW_STATE_SESSION_TOKEN_SECURE_RANDOM_ALGORITM`: 
2.2:
[https://github.com/apache/myfaces/blob/2.2.x/impl/src/main/java/org/apache/myfaces/application/viewstate/ServerSideStateCacheImpl.java#L180]
2.3:
[https://github.com/apache/myfaces/blob/2.3.x/impl/src/main/java/org/apache/myfaces/application/viewstate/ServerSideStateCacheImpl.java#L172]
3.0:
[https://github.com/apache/myfaces/blob/3.0.x/impl/src/main/java/org/apache/myfaces/application/viewstate/ServerSideStateCacheImpl.java#L171]
 

It looks like this one was fixed in 4.0 via this commit 
[https://github.com/apache/myfaces/commit/b27eb9644e5c7b8fd7758a9304c780cd54a36f48]

> Context Parameter Spelling Error: ALGORITM
> ------------------------------------------
>
>                 Key: MYFACES-4727
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4727
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.2.15, 3.0.2, 2.3.11, 2.3-next-M8, 4.0.3, 4.1.1
>            Reporter: Volodymyr Siedlecki
>            Priority: Major
>
> The context paramters below are misspelled.  They should have an H. 
> ALGORIT{*}H{*}M.
> The are documented and coded the same way. However, it's still a spelling 
> error. 
> They documented as so:
> 2.0:
> o.a.m.RANDOM_KEY_IN_VIEW_STATE_SESSION_TOKEN_SECURE_RANDOM_ALGORI{*}TM{*}
> 2.2, 2.3 and 3.0
> o.a.m.RANDOM_KEY_IN_CSRF_SESSION_TOKEN_SECURE_RANDOM_ALGORI{*}TM{*}
> o.a.m.RANDOM_KEY_IN_VIEW_STATE_SESSION_TOKEN_SECURE_RANDOM_ALGORI{*}TM{*}
> 4.0+
> o.a.m.RANDOM_KEY_IN_CSRF_SESSION_TOKEN_SECURE_RANDOM_ALGORI{*}TM{*}
> I propose fixing it 5.0 by adding new parameters while deprecating the 
> misspelled names for that release. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to