Mailing-List: contact commits-help@wicket.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@wicket.apache.org
Message-ID: <1001540253.1228135425137.JavaMail.jira@brutus>
Date: Mon, 1 Dec 2008 04:43:45 -0800 (PST)
From: "Timo Rantalaiho (JIRA)" <jira@apache.org>
To: commits@wicket.apache.org
Subject: [jira] Updated: (WICKET-1886) WicketTester Cookie handling
In-Reply-To: <485871795.1224679844232.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/WICKET-1886?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timo Rantalaiho updated WICKET-1886:
------------------------------------

        Fix Version/s: 1.4-RC2
    Affects Version/s:     (was: 1.3.4)
                       1.3.5
                       1.4-RC1

> 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=C3=B6rn Zaefferer
>            Assignee: Timo Rantalaiho
>             Fix For: 1.3.6, 1.4-RC2
>
>         Attachments: CookieTest.java, patch-WICKET-1886.diff, WICKET-1886=
__SecureForm_and_failing_test.patch
>
>
> While trying to test my SecureForm implementation (https://issues.apache.=
org/jira/browse/WICKET-1885) with WicketTester I ran into this issue: A coo=
kie 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 wa=
y its possible to set a cookie in the response and read it from the request=
.
> A simple testcase is attached.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.