You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Bertrand Guay-Paquet (JIRA)" <ji...@apache.org> on 2011/03/29 22:42:05 UTC
[jira] [Created] (WICKET-3576) Cannot set a cookie on bookmarkable
page
Cannot set a cookie on bookmarkable page
----------------------------------------
Key: WICKET-3576
URL: https://issues.apache.org/jira/browse/WICKET-3576
Project: Wicket
Issue Type: Bug
Components: wicket-core, wicket-examples
Affects Versions: 1.5-RC3, 1.5-RC2
Environment: wicket-examples from rev 1086031 (March 29 2011)
Reporter: Bertrand Guay-Paquet
Priority: Critical
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 of actually sign-in at all. The same sign-in page is presented a second time. Sign-in works on this second page.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-3576) Cannot set a cookie on
bookmarkable page
Posted by "Bertrand Guay-Paquet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012691#comment-13012691 ]
Bertrand Guay-Paquet commented on WICKET-3576:
----------------------------------------------
Some debugging reveals that the BufferedWebResponse is reset which has the effect of discarding previously added AddCookieActions.
This happens at :
WebPageRenderer.redirectTo(Url, RequestCycle) line: 176
(partial) stack trace:
BufferedWebResponse.sendRedirect(String) line: 460
HeaderBufferingWebResponse.sendRedirect(String) line: 111
WebPageRenderer.redirectTo(Url, RequestCycle) line: 177
WebPageRenderer.respond(RequestCycle) line: 254
RenderPageRequestHandler.respond(IRequestCycle) line: 139
RequestCycle$HandlerExecutor.respond(IRequestHandler) line: 715
RequestCycle$HandlerExecutor(RequestHandlerStack).execute(IRequestHandler) line: 63
RequestCycle$HandlerExecutor(RequestHandlerStack).execute(IRequestHandler) line: 96
CustomRequestCycle(RequestCycle).processRequest() line: 212
CustomRequestCycle(RequestCycle).processRequestAndDetach() line: 253
WicketFilter.processRequest(ServletRequest, ServletResponse, FilterChain) line: 138
Execution passes by
WebPageRenderer.respond(RequestCycle) line: 254
which has the following:
else if (!targetUrl.equals(currentUrl) //
&&
(getPageProvider().isNewPageInstance() || (isSessionTemporary() && getPage().isPageStateless())))
{
// if target URL is different and session is temporary and page is stateless
// this is special case when page is stateless but there is no session so we can't
// render it to buffer
// alternatively if URLs are different and we have a page class and not an instance we
// can redirect to the url which will instantiate the instance of us
// note: if we had session here we would render the page to buffer and then redirect to
// URL generated *after* page has been rendered (the statelessness may change during
// render). this would save one redirect because now we have to render to URL generated
// *before* page is rendered, render the page, get URL after render and if the URL is
// different (meaning page is not stateless), save the buffer and redirect again (which
// is pretty much what the next step does)
redirectTo(targetUrl, requestCycle);
}
WICKET-3161 had a similar problem.
> Cannot set a cookie on bookmarkable page
> ----------------------------------------
>
> Key: WICKET-3576
> URL: https://issues.apache.org/jira/browse/WICKET-3576
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core, wicket-examples
> Affects Versions: 1.5-RC2, 1.5-RC3
> Environment: wicket-examples from rev 1086031 (March 29 2011)
> Reporter: Bertrand Guay-Paquet
> Priority: Critical
> Labels: cookie
>
> 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 of actually sign-in at all. The same sign-in page is presented a second time. Sign-in works on this second page.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-3576) Cannot set a cookie on
bookmarkable page
Posted by "Bertrand Guay-Paquet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015448#comment-13015448 ]
Bertrand Guay-Paquet commented on WICKET-3576:
----------------------------------------------
I have just updated to rev. 1088594 (8:28:17 AM, April-04-11) and I still have the problem.
The steps must be followed exactly however :
1-Start "org.apache.wicket.examples.StartExamples.java"
2-Open the page at http://localhost:8080/authentication2/wicket/bookmarkable/org.apache.wicket.examples.authentication2.SignIn2
3-Log-in
4-Log-in successful but the "remember me" cookie named "LoggedIn" is not set; only JSESSIONID is set.
After this however,
5-Click "sign out"
6-Click "Home"
7-Log-in
8-"LoggedIn" cookie is not set.
Is this what you have tried?
> Cannot set a cookie on bookmarkable page
> ----------------------------------------
>
> Key: WICKET-3576
> URL: https://issues.apache.org/jira/browse/WICKET-3576
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core, wicket-examples
> Affects Versions: 1.5-RC2, 1.5-RC3
> Environment: wicket-examples from rev 1086031 (March 29 2011)
> Reporter: Bertrand Guay-Paquet
> Priority: Critical
> Labels: cookie
>
> 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 of actually sign-in at all. The same sign-in page is presented a second time. Sign-in works on this second page.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-3576) Cannot set a cookie on
bookmarkable page
Posted by "Juergen Donnerstag (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015178#comment-13015178 ]
Juergen Donnerstag commented on WICKET-3576:
--------------------------------------------
I've tested the latest snapshot 1.5rc3 on wicket-library. Seems to be fixed
> Cannot set a cookie on bookmarkable page
> ----------------------------------------
>
> Key: WICKET-3576
> URL: https://issues.apache.org/jira/browse/WICKET-3576
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core, wicket-examples
> Affects Versions: 1.5-RC2, 1.5-RC3
> Environment: wicket-examples from rev 1086031 (March 29 2011)
> Reporter: Bertrand Guay-Paquet
> Priority: Critical
> Labels: cookie
>
> 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 of actually sign-in at all. The same sign-in page is presented a second time. Sign-in works on this second page.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WICKET-3576) Cannot set a cookie on bookmarkable
page
Posted by "Bertrand Guay-Paquet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Guay-Paquet updated WICKET-3576:
-----------------------------------------
Attachment: setCookie_failing_test.patch
Test case demonstrating the problem
> Cannot set a cookie on bookmarkable page
> ----------------------------------------
>
> Key: WICKET-3576
> URL: https://issues.apache.org/jira/browse/WICKET-3576
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core, wicket-examples
> Affects Versions: 1.5-RC2, 1.5-RC3
> Environment: wicket-examples from rev 1086031 (March 29 2011)
> Reporter: Bertrand Guay-Paquet
> Priority: Critical
> Labels: cookie
> Attachments: setCookie_failing_test.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-3576) Cannot set a cookie on
bookmarkable page
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014029#comment-13014029 ]
Martin Grigorov commented on WICKET-3576:
-----------------------------------------
Did you try it with RC-3 ?
Because this looks like WICKET-3493 which is fixed for RC3
> Cannot set a cookie on bookmarkable page
> ----------------------------------------
>
> Key: WICKET-3576
> URL: https://issues.apache.org/jira/browse/WICKET-3576
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core, wicket-examples
> Affects Versions: 1.5-RC2, 1.5-RC3
> Environment: wicket-examples from rev 1086031 (March 29 2011)
> Reporter: Bertrand Guay-Paquet
> Priority: Critical
> Labels: cookie
>
> 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 of actually sign-in at all. The same sign-in page is presented a second time. Sign-in works on this second page.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-3576) Cannot set a cookie on
bookmarkable page
Posted by "Bertrand Guay-Paquet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018577#comment-13018577 ]
Bertrand Guay-Paquet commented on WICKET-3576:
----------------------------------------------
Works wonderfully, thanks!
Closing issue
> Cannot set a cookie on bookmarkable page
> ----------------------------------------
>
> Key: WICKET-3576
> URL: https://issues.apache.org/jira/browse/WICKET-3576
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core, wicket-examples
> Affects Versions: 1.5-RC2, 1.5-RC3
> Environment: wicket-examples from rev 1086031 (March 29 2011)
> Reporter: Bertrand Guay-Paquet
> Assignee: Juergen Donnerstag
> Priority: Critical
> Labels: cookie
> Fix For: 1.5-RC4
>
> Attachments: setCookie_failing_test.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WICKET-3576) Cannot set a cookie on bookmarkable
page
Posted by "Bertrand Guay-Paquet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Guay-Paquet updated WICKET-3576:
-----------------------------------------
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.
was:
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 of actually sign-in at all. The same sign-in page is presented a second time. Sign-in works on this second page.
> Cannot set a cookie on bookmarkable page
> ----------------------------------------
>
> Key: WICKET-3576
> URL: https://issues.apache.org/jira/browse/WICKET-3576
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core, wicket-examples
> Affects Versions: 1.5-RC2, 1.5-RC3
> Environment: wicket-examples from rev 1086031 (March 29 2011)
> Reporter: Bertrand Guay-Paquet
> Priority: Critical
> Labels: cookie
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (WICKET-3576) Cannot set a cookie on bookmarkable
page
Posted by "Bertrand Guay-Paquet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Guay-Paquet closed WICKET-3576.
----------------------------------------
> Cannot set a cookie on bookmarkable page
> ----------------------------------------
>
> Key: WICKET-3576
> URL: https://issues.apache.org/jira/browse/WICKET-3576
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core, wicket-examples
> Affects Versions: 1.5-RC2, 1.5-RC3
> Environment: wicket-examples from rev 1086031 (March 29 2011)
> Reporter: Bertrand Guay-Paquet
> Assignee: Juergen Donnerstag
> Priority: Critical
> Labels: cookie
> Fix For: 1.5-RC4
>
> Attachments: setCookie_failing_test.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-3576) Cannot set a cookie on
bookmarkable page
Posted by "Bertrand Guay-Paquet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014160#comment-13014160 ]
Bertrand Guay-Paquet commented on WICKET-3576:
----------------------------------------------
I cannot locate which revision is RC3. I looked in the subversion "Releases" folder and couldn't find it.
However, my test environment was Wicket rev #1086031 (latest on March 29 2011) . From what I can see in the log of WICKET-3493, the last commit was done in rev #1079685. I guess this means I had the relevant changes?
> Cannot set a cookie on bookmarkable page
> ----------------------------------------
>
> Key: WICKET-3576
> URL: https://issues.apache.org/jira/browse/WICKET-3576
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core, wicket-examples
> Affects Versions: 1.5-RC2, 1.5-RC3
> Environment: wicket-examples from rev 1086031 (March 29 2011)
> Reporter: Bertrand Guay-Paquet
> Priority: Critical
> Labels: cookie
>
> 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 of actually sign-in at all. The same sign-in page is presented a second time. Sign-in works on this second page.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-3576) Cannot set a cookie on
bookmarkable page
Posted by "Michael Day (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016857#comment-13016857 ]
Michael Day commented on WICKET-3576:
-------------------------------------
I believe this bug affects my application in that users cannot log out because the "LoggedIn" cookie is never unset when I call session.invalidate() and then setResponsePage().
> Cannot set a cookie on bookmarkable page
> ----------------------------------------
>
> Key: WICKET-3576
> URL: https://issues.apache.org/jira/browse/WICKET-3576
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core, wicket-examples
> Affects Versions: 1.5-RC2, 1.5-RC3
> Environment: wicket-examples from rev 1086031 (March 29 2011)
> Reporter: Bertrand Guay-Paquet
> Priority: Critical
> Labels: cookie
> Attachments: setCookie_failing_test.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WICKET-3576) Cannot set a cookie on bookmarkable
page
Posted by "Juergen Donnerstag (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juergen Donnerstag resolved WICKET-3576.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.5-RC4
Assignee: Juergen Donnerstag
> Cannot set a cookie on bookmarkable page
> ----------------------------------------
>
> Key: WICKET-3576
> URL: https://issues.apache.org/jira/browse/WICKET-3576
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core, wicket-examples
> Affects Versions: 1.5-RC2, 1.5-RC3
> Environment: wicket-examples from rev 1086031 (March 29 2011)
> Reporter: Bertrand Guay-Paquet
> Assignee: Juergen Donnerstag
> Priority: Critical
> Labels: cookie
> Fix For: 1.5-RC4
>
> Attachments: setCookie_failing_test.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-3576) Cannot set a cookie on
bookmarkable page
Posted by "Bertrand Guay-Paquet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015471#comment-13015471 ]
Bertrand Guay-Paquet commented on WICKET-3576:
----------------------------------------------
Please see newly attached test case for an even simpler way to reproduce.
> Cannot set a cookie on bookmarkable page
> ----------------------------------------
>
> Key: WICKET-3576
> URL: https://issues.apache.org/jira/browse/WICKET-3576
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core, wicket-examples
> Affects Versions: 1.5-RC2, 1.5-RC3
> Environment: wicket-examples from rev 1086031 (March 29 2011)
> Reporter: Bertrand Guay-Paquet
> Priority: Critical
> Labels: cookie
> Attachments: setCookie_failing_test.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira