[
https://issues.apache.org/jira/browse/WICKET-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581412#comment-13581412
]
Martin Grigorov commented on WICKET-4989:
-----------------------------------------
One more thing that I believe is wrong in the current handling: some tests
assert that a response cookie is in the response even after a redirect.
A browser wont keep the cookie in all responses. It will be just in the first
response (the redirect one) and from there on only the request headers will
have the cookie, but not the headers for all following responses.
I didn't change this behavior because it may break user applications.
> WicketTester should send copies of its cookies
> -----------------------------------------------
>
> Key: WICKET-4989
> URL: https://issues.apache.org/jira/browse/WICKET-4989
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.9, 6.4.0
> Environment: any
> Reporter: Michael Mosmann
> Assignee: Martin Grigorov
> Fix For: 6.7.0, 1.5.10
>
> Attachments: quickstart-basewickettester-bug.zip
>
>
> There are some bugs related to cookie handling in BaseWicketTester.
> Problem 1) a cookie set in the request should not be in the response unless
> manually set by the server code
> Problem 2) wicket tester sends the original cookie instance to the server. If
> the server code manipulates the cookie anyhow (e.g. change its value) but do
> not send it back explicitly in the response then the original cookie in
> WicketTester (the request cookie) is updated while it shouldn't be.
> A possible solutions for these problems can be found at:
> https://github.com/apache/wicket/pull/28
--
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
