[PORTLETBRIDGE-156] Encoding Public render parameters in a render redirect done incorrectly if url already action encoded

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-alpha
• Fix Version/s: 2.0.0-beta
• Component/s: Impl
• Assignee: Michael Freedman
• Reporter: Michael Freedman
• Created: 29/Jul/10 15:24
• Updated: 29/Jul/10 16:00
• Resolved: 29/Jul/10 16:00

Description

If you issue a render redirect on an url that you have already called encodeActionURL on the bridge screws up big time because it merely encodes the extra public render parameters to the end of the passed in url as part of a query string. This (obviously) changes the url so that it no longer matches when used as the key to lookup the request attribute to see if this url is already action encoded. Since we don't think its action encoded (but it is) we go ahead an re-encode it turning the resulting redirect url into garbage.

Fix is to delay adding the public render parameters to the url until after the check to see if already action encoded. When already encoded add the PRP to the querystring object that is added to the request (attribute) otherwise add to the query string.