[ 
https://issues.apache.org/jira/browse/WICKET-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647320#action_12647320
 ] 

Jörn Zaefferer commented on WICKET-1886:
----------------------------------------

In testing a form where Cookies are required the flow is REQUEST ---> RESPONSE 
---> REQUEST ---> RESPONSE ---> REQUEST and so on. So I need a way to simulate 
that flow and get the cookies from one response into the the next request.

I don't care about the semantics, as long as I can test my form with 
WicketTester instead of a browser. I'd be happy to manually "transfer" the 
cookie, but haven't found any way to do that.

> WicketTester Cookie handling
> ----------------------------
>
>                 Key: WICKET-1886
>                 URL: https://issues.apache.org/jira/browse/WICKET-1886
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.3.4
>            Reporter: Jörn Zaefferer
>            Assignee: Timo Rantalaiho
>             Fix For: 1.3.6
>
>         Attachments: CookieTest.java
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.

Reply via email to