Here's a fun bug in Wicket I stumbled on while implementing a new way to authenticate the user which is much easier to understand.
This is a page to resolve the intended authentication target URL when the authenticating user is blocking Cookies.
The application has mounted a page at AuthService, which may set a resolve page as render page. When using WebPage.setResponsePage() from on override of prepareForRender(), the returned content is exactly two HTML pages.
When moving the call to setResponsePage into the constructor of the original page, the problem is solved in the browswer, but nothing in the WicketTester works.
This is a page to resolve the intended authentication target URL when the authenticating user is blocking Cookies.
The application has mounted a page at AuthService, which may set a resolve page as render page. When using WebPage.setResponsePage() from on override of prepareForRender(), the returned content is exactly two HTML pages.
When moving the call to setResponsePage into the constructor of the original page, the problem is solved in the browswer, but nothing in the WicketTester works.
0 comments:
Post a Comment