[
https://issues.apache.org/jira/browse/WICKET-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204422#comment-13204422
]
Christoph Leiter commented on WICKET-4398:
------------------------------------------
The committed fix doesn't solve the problem completely. A request to /?a&+ or
/?a&%20 triggers the same exception.
> Any empty url-parameter will make wicket 1.5 crash
> --------------------------------------------------
>
> Key: WICKET-4398
> URL: https://issues.apache.org/jira/browse/WICKET-4398
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.3
> Reporter: Johannes Odland
> Assignee: Martin Grigorov
> Fix For: 1.5.5, 6.0.0
>
> Attachments: WICKET-4398-2.patch, WICKET-4398.patch
>
>
> Adding an empty parameter to the query string will make wicket crash.
> http://www.example.com/?oneParam&;
> How to reproduce in test:
> PageParameters params = new PageParameters();
> params.set("","");
> params.getAllNamed();
> Cause:
> Wicket accepts empty parameters, but when encoding the url for a rendered
> page it will call params.getAllNamed().
> params.getAllNamed() instantiates new NamedPairs, which calls Args.notEmpty()
> on the key during instantiation, causing the application to crash.
> The NamedPair constructor should probably allow empty string as a key, and
> call Args.notNull() on the key in stead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
