You are viewing a plain text version of this content. The canonical link for it is here.

Posted to pluto-dev@portals.apache.org by "Ulrich Küster (JIRA)" <pl...@jakarta.apache.org> on 2005/07/13 11:18:15 UTC

[jira] Updated: (PLUTO-137) RenderParameter Encoding

     [ http://issues.apache.org/jira/browse/PLUTO-137?page=all ]

Ulrich Küster updated PLUTO-137:
--------------------------------

    Attachment: jira137Apatch.txt

Small patch that takes care of issue A

> RenderParameter Encoding
> ------------------------
>
>          Key: PLUTO-137
>          URL: http://issues.apache.org/jira/browse/PLUTO-137
>      Project: Pluto
>         Type: Bug
>   Components: portal driver
>     Versions: Current CVS
>     Reporter: Ulrich Küster
>  Attachments: jira137Apatch.txt
>
> This is a bug that is somewhat related to http://issues.apache.org/jira/browse/PLUTO-119.
> org.apache.pluto.portalImpl.core.PortalControlParameters does some form of encoding to prevent parameter values from conflicting with the way, Pluto encodes parameters into urls. E.g. "_" will be replaced by "0x1".
> A)
> If a parameter value contains e.g the String "0x1" like "myParam0x1" right away, it will be wrongly decoded to "myParam_" since the String "0x" is not decoded right away.
> B)
> Parameter values are decoded, parameter names are not. Therefore setting a render parameter with a name like "/_rp_" causes Plutos parameter parsing algorithm to fail and all subsequent render parameters will be missing from the parameters collection.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira