[WICKET-6929] User forced to log in twice after checking WebClientInfo

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Not A Problem
• Affects Version/s: 9.5.0
• Component/s: wicket-core
• Labels: WebClientInfo
• Environment: Windows 10 Enterprise, JDK 11.0.7, NetBeans 11.3 and Payara 5.201
• External issue URL: https://stackoverflow.com/questions/69451441/wicket-9-user-forced-to-log-in-again-when-accessing-a-certain-page-for-first-ti

Language

java javascript

• Assignee: Sven Meier
• Reporter: Sushila Burgess
• Created: 01/Nov/21 13:18
• Updated: 08/Nov/21 13:18
• Resolved: 05/Nov/21 20:31

Description

We found that in Wicket 9, an intermittent error occurred which forced our users
to log in twice, even though they were definitely already correctly logged in
and their session had not expired. (This error did not occur in Wicket 1.5.)

We have found that this error is associated with checking WebClientInfo
properties. In the course of redirection to and from BrowserInfoPage, it seems
as if the user's login credentials somehow get lost.

We have found a work-round, which is to check WebClientInfo properties before
login. However, the disadvantage of this is that every single user sees the
following message for perhaps a second as they first log in:

"If you see this, it means both JavaScript and meta-refresh are not support by
your browser configuration. Please click this link to continue to the original
destination."

We have attempted to reproduce this error in a simple quick-start application.
We can reproduce it reliably on first opening Chrome or Edge on localhost.
In the current, simple application, we cannot reproduce it when visiting a URL
with a fully qualified domain name, but it did occur, intermittently, in the
full-scale application.

The quick-start application is attached as a zip file. Please see the README.txt of that application for a few more details.