[
https://issues.apache.org/jira/browse/WICKET-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-4865.
-------------------------------------
Resolution: Fixed
Fix Version/s: 6.3.0
Assignee: Martin Grigorov
The patch is applied with minor improvements. Please test it today if you can.
Additionally I see there is no test for the described issue in the mailing
list. It would be good to have one to prevent any regressions in the future.
Thanks!
> Page parameters not working with CryptoMapper
> ---------------------------------------------
>
> Key: WICKET-4865
> URL: https://issues.apache.org/jira/browse/WICKET-4865
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.2.0
> Reporter: Jesse Long
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 6.3.0
>
> Attachments: WICKET-4865.patch
>
>
> When CryptoMapper is used, page parameters do not work. This is because the
> incorrect request is set in the request cycle. The incorrect request contains
> the encrypted url, where the page parameters are encoded into the url
> segments. When the CryptoMapper maps a url to a request handler, it should
> set the request to the correct request when the request handler is selected.
> This was reported on the users@ list, but I have also fallen victim to it
> when getting urlFor(resourceReference, pageParameters) and the pageParameters
> not comming out on the other end.
> See:
> http://mail-archives.apache.org/mod_mbox/wicket-users/201211.mbox/%[email protected]%3E
> https://github.com/jesselong/wicket/commits/for-apache-master-pr-4 (3 commits)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
