[
https://issues.apache.org/jira/browse/WICKET-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989318#comment-12989318
]
Pedro Santos edited comment on WICKET-1886 at 2/1/11 6:42 PM:
--------------------------------------------------------------
The problem was that I was not assigning the redirect request cycle to the
"cycle" variable that is used latter to generate the lastRenderedPage.
Robert is right, I'm sending the patch with the test case and fix calling the
setupRequestAndResponse to create the request. Inside this method cookies are
already copied from those on session.
was (Author: pedrosans):
The problem was that I was not assigning the request redirect request cycle
to the cycle variable that is used latter to generate the lastRenderedPage.
Robert is right, I'm sending the patch with the test case and fix using the
setupRequestAndResponse to create the request. Inside this method cookies are
already copied from those on session.
> WicketTester Cookie handling
> ----------------------------
>
> Key: WICKET-1886
> URL: https://issues.apache.org/jira/browse/WICKET-1886
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.3.5, 1.4-RC1
> Reporter: Jörn Zaefferer
> Assignee: Pedro Santos
> Fix For: 1.3.6, 1.4-RC2
>
> Attachments: CookieTest.java, WICKET-1886-test-fix.patch,
> WICKET-1886.patch, WICKET-1886__SecureForm_and_failing_test.patch,
> patch-WICKET-1886.diff
>
>
> While trying to test my SecureForm implementation
> (https://issues.apache.org/jira/browse/WICKET-1885) with WicketTester I ran
> into this issue: A cookie set in the response never shows up in the "next"
> request, because both have their own lists of cookies that aren't shared.
> Afaik both should share the same List instance to handle cookies. That way
> its possible to set a cookie in the response and read it from the request.
> A simple testcase is attached.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
