[
https://issues.apache.org/jira/browse/MYFACES-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volodymyr Siedlecki resolved MYFACES-4404.
------------------------------------------
Resolution: Fixed
Fixed in **
[2.2.15|https://issues.apache.org/jira/issues/?jql=project+%3D+MYFACES+AND+fixVersion+%3D+2.2.15],
[2.3.10|https://issues.apache.org/jira/issues/?jql=project+%3D+MYFACES+AND+fixVersion+%3D+2.3.10],
[2.3-next-M7|https://issues.apache.org/jira/issues/?jql=project+%3D+MYFACES+AND+fixVersion+%3D+2.3-next-M7],
[3.0.2|https://issues.apache.org/jira/issues/?jql=project+%3D+MYFACES+AND+fixVersion+%3D+3.0.2]
> Log ViewState String Before Sending Response
> --------------------------------------------
>
> Key: MYFACES-4404
> URL: https://issues.apache.org/jira/browse/MYFACES-4404
> Project: MyFaces Core
> Issue Type: Improvement
> Components: JSR-344, JSR-372
> Affects Versions: 2.2.14, 2.3.9
> Reporter: Volodymyr Siedlecki
> Assignee: Volodymyr Siedlecki
> Priority: Trivial
> Fix For: 2.2.15, 2.3.10, 2.3-next-M7, 3.0.2
>
>
> When debugging JSF, it's very useful to know of the viewstate string has been
> altered in any way. Users can have filters that change that viewstate
> (filter out ='s, for example). This then causes decoding/decryption errors.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)