Right, it's request parameters from form values sent as part of an HTTP POST that are problematic.
On 1/24/07, Frank Villarreal <[EMAIL PROTECTED]> wrote:
Hello David, Yes I do encode my uris with the <portlet:actionURL> tag or with the PortletURL class (one and the same I believe). But that's not the issue. The uris work fine. It's the "other" fields on a page that are "unencodable" that are the problem ... for instance user-input in HTML <input> fields. I came across this error once I started coding some heavy-duty data collection applications ... and noticed that the wrong portlets were seeing the submitted data! - Frank > -----Original Message----- > From: David Sean Taylor [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 24, 2007 02:08 PM > To: Jetspeed Users List > Subject: Re: SEVERE ERROR: RenderRequest Parameters > > > > Have you considered the standard way to encode render parameters with > action or render URLs > > <portlet:actionURL var="nodeLink" > > <portlet:param name="node" value="${name}" /> > </portlet:actionURL> The information contained in this e-mail is confidential and is intended only for the use of the individual or entity to which it is addressed. Dissemination, distribution, copying or use of this e-mail is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete the message from your system. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
