Details
-
Type:
Bug
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 2.2.1
-
Fix Version/s: None
-
Component/s: Core: Flow Executor
-
Labels:None
Description
When I do a flowRedirect and add a GET parameter with a non-ascii character, the parameter arrives badly encoded (or decoded) at the destination flow.
Example:
<end-state id="finish" view="flowRedirect:newflow?param=#{criteria}" />
When #
{criteria} resolves as "ΓΌ", it arrives at flow "newflow" as 2 different characters.The following works correctly:
" />