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

Posted to commits@wicket.apache.org by "Jean-Baptiste Quenot (JIRA)" <ji...@apache.org> on 2007/03/06 15:01:36 UTC

[jira] Assigned: (WICKET-193) different behaviour to PageParameters encoding/ decoding

     [ https://issues.apache.org/jira/browse/WICKET-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Quenot reassigned WICKET-193:
-------------------------------------------

    Assignee: Jean-Baptiste Quenot

> different behaviour to PageParameters encoding/ decoding
> --------------------------------------------------------
>
>                 Key: WICKET-193
>                 URL: https://issues.apache.org/jira/browse/WICKET-193
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.3, 2.0
>         Environment: all
>            Reporter: Korbinian Bachl
>         Assigned To: Jean-Baptiste Quenot
>
> i noticed that wicket encodes all PageParameters for a page using the IndexedParamUrlCodingStrategy, but never decodes it, so you get the input raw, wich is opposite of the behaviour of BookmarkablePageRequestTargetUrlCodingStrategy where all parameters are encoded and decoded completely - this give great problems in developement as well as the lock to a single strategy in bigger projects as you would need to manually fix it every time you switch.
> Furthermore:  "We should look at the complete encode/decode story anyway. Now it is done in numerous places some like String.replace("&", "&amp;") and here a decode there a encode. This should all be done for the complete url itself i think in one place (instead per parameter or value)" - JCompagner

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.