You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Pedro Santos (JIRA)" <ji...@apache.org> on 2011/02/01 13:12:29 UTC

[jira] Updated: (WICKET-1886) WicketTester Cookie handling

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

Pedro Santos updated WICKET-1886:
---------------------------------

    Attachment: WICKET-1886.patch

Wicket tester don't set the cookies on request after an redirect response, test case showing the problem

> 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.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