Incorrectly encoded redirect URLs
-
I’m trying to use the “Redirect” option under “Confirmation.” When I put in a URL like:
http://www.example.com/search?param1=foo¶m2=bar…the redirect sends the user to:
http://www.example.com/search?param1=foo¶m2=barThe
&has been incorrectly encoded to&, breaking the target page.Is this the expected behavior? If not, is there a workaround?
Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
The topic ‘Incorrectly encoded redirect URLs’ is closed to new replies.