[WICKET-3576] Cannot set a cookie on bookmarkable page

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.5-RC2, 1.5-RC3
• Fix Version/s: 1.5-RC4
• Component/s: wicket, wicket-examples
• Labels: cookie
• Environment: wicket-examples from rev 1086031 (March 29 2011)
• Assignee: Juegen Donnerstag
• Reporter: Bertrand Guay-Paquet
• Created: 29/Mar/11 20:41
• Updated: 22/Apr/11 05:23
• Resolved: 09/Apr/11 14:45

Description

Steps to reproduce:
//////////////////////
After starting the Wicket Examples, navigate directly to:
http://localhost:8080/authentication2/wicket/bookmarkable/org.apache.wicket.examples.authentication2.SignIn2

Sign in with proper user name and password. Notice that the cookie "LoggedIn" is not set.
//////////////////////

This does not happen if navigation to the authentication2 example is done through the examples home page. In that case, the URL is http://localhost:8080/authentication2/.

If I understand correctly, this means that bookmarkable pages cannot set cookies when they also do a redirect. e.g. a bookmarkable sign-in page.

Note that with the examples from 1.5-rc2, doing the steps described above produces a different result. In that case, signing-in does not set a cookie or actually sign-in at all. The same sign-in page is presented a second time. Sign-in works on this second page.

Issue Links

• is duplicated by: WICKET-3631 invoking setResponsePage after setting cookie results in cookie not being created(no Set-Cookie header being sent to the client).