allow ampersand escaped url in requestURI attribute

fabrizio giustina added a comment - 03/Apr/06 3:10 PM > http://my.portal/myapp?portalparam1=param1&portalparam2=param2 an escaped ampersand is not valid in the url: it needs to be escaped in the document, but the browser should unescape it before following the link and sending the request to the server, so http://my.portal/myapp?portalparam1=param1&portalparam2=param2 IS the same as http://my.portal/myapp?amp;portalparam2=param1&portalparam1=param1 Where are you seeing this problem? How the escaped ampersand is passed to displaytag, is this the behaviour of a specific portal server?

Luca Barozzi added a comment - 04/Apr/06 2:15 AM Well, this were the code, in a JSP, creating the problem before the replaceAll("&amp;", "&") were added. [...]         PortletURL listUrl = renderResponse.createActionURL();         listUrl.setParameter("PAGE", "PROJECTPAGE");         listUrl.setParameter("SOURCE", "ProjectsList");         listUrl.setParameter("COMMAND", "LIST"); => pageContext.setAttribute("listUrl", listUrl.toString().replaceAll("&amp;", "&")); [...]         <dt:table id="progetto" class="list"                 name="${progetti}" requestURI="${listUrl}"                 requestURIcontext="false" excludedParams="*"> [...]         </dt:table> [...] the portal is eXo and listUrl contains "&amp;" as of given example. The parameter il passed to the table tag as the requestURI attribute and not unescaped by the browser before string tokenizing.

fabrizio giustina added a comment - 16/Dec/07 3:48 PM escaped ampersands (&amp;) must not be used in tag attributes. The methot you were using was escaping ampersands because it was intended to produce urls to be used in html links.