[
https://issues.apache.org/jira/browse/WICKET-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
George Armhold updated WICKET-3800:
-----------------------------------
Attachment: stateless-form-bug.tar.gz
quickstart project
> StatelessForm + IndexedParamUrlCodingStrategy: URL path params are not
> url-encoded
> ----------------------------------------------------------------------------------
>
> Key: WICKET-3800
> URL: https://issues.apache.org/jira/browse/WICKET-3800
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.4.17
> Environment: embedded jetty, glassfish 3.1
> Reporter: George Armhold
> Attachments: stateless-form-bug.tar.gz
>
>
> When using a StatelessForm on a page mounted with
> IndexedParamUrlCodingStrategy/MixedParamUrlCodingStrategy, parameters added
> to the URL path are not url-encoded.
> It's actually coming from RequestCycle.urlFor(). There is a note on line 917
> of that file indicating "Do not encode values here. It is the encoder's job
> to do the endoding". So perhaps I'm doing something wrong, but I'm surprised
> to see different behavior when the form is stateless.
> Another user reported what I believe is probably the same issue here:
> http://apache-wicket.1842946.n4.nabble.com/StatelessForm-problem-Not-all-parameters-were-encoded-td1887698.html
> In that thread Igor responded "forms do not support indexed strategies since
> they need actual parameternames", which frankly, I do not understand. I'm
> adding parameters like:
> PageParameters params = new PageParameters();
> params.add("0", input0.getModelObject());
> setResponsePage(HomePage.class, params);
> and I assume that "0" qualifies as a named parameter.
> I will attach a quickstart to demonstrate.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
