[jira] Closed: (WW-1751) StrutsResultSupport truncates redirect url at &

["Dale Newfield (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/struts/browse/WW-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dale Newfield closed WW-1751.
-----------------------------


I had not tested this since the 2.0.5 -> 2.0.6 upgrade.  It does appear to work correctly now.  Sorry to have you chasing ghosts!

> StrutsResultSupport truncates redirect url at &
> ---------------------------------------------------
>
>                 Key: WW-1751
>                 URL: https://issues.apache.org/struts/browse/WW-1751
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Configuration, Dispatch
>    Affects Versions: 2.0.5
>         Environment: My dev environment is tomcat5.5 on OSX using java5
>            Reporter: Dale Newfield
>         Assigned To: Don Brown
>            Priority: Minor
>
> I would expect this to be a fairly common use case, but I've been unable to find anybody else with this problem.
> I've got an action where I would like to redirect to another action on success, but I'm unable to pass more than one argument to that second action.
> <action name="setCommunityIcon" class="communityAction" method="setNewIcon">
>   <result name="success" type="redirect">
>     <param name="location">cropIcon.xhtml?code=${mediaCode}&amp;displayType=Community</param>
>     <param name="parse">true</param>
>   </result>
>   <result name="badID">/404.jsp</result>
> </action>
> Instead of redirecting to "/cropIcon.xhtml?code=FOO&displayType=Community" it redirects to "/cropIcon.xhtml?code=FOO" .  I have tried lots of variations.  Without the "amp;" part, struts.xml fails to parse.  If I reverse the two arguments it still truncates right where the & should be (so instead of going to "/cropIcon.xhtml?displayType=Community&code=FOO" it goes to "/cropIcon.xhtml?displayType=Community").
> (I see the same behavior if the encode param is passed in, too.)
> I assume I can work around this by having the OGNL expression generate the &, but it seems strange that that is the only way...
> Any suggestions?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.