[
https://issues.apache.org/jira/browse/WICKET-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17440449#comment-17440449
]
Sushila Burgess commented on WICKET-6929:
-----------------------------------------
Actually I have found that in some circumstances it *is* a problem. It is a
problem that you can work round. That doesn't mean that there is no problem at
all.
Sven, you have clarified that Chrome (unlike Firefox) redirects the user to
their Home page from BrowserInfoPage. That is fine if they wanted to go to
their Home page. But what if their original destination was somewhere else?
I have now adapted my debug application to demonstrate this. After logging in,
there are now 3 pages: (1) home page; (2) intermediate page; (3) final page,
which checks WebClientInfo properties. The user can navigate via links from
page 1 to 2, then from page 2 to 3.
However, the first time after opening Chrome or Edge, an attempt to visit page
3 sends the user back to page 1 again.
This does not seem to match the documentation, which claims that the user will
be redirected from BrowserInfoPage to their original destination.
If you would like me to upload my updated application so you can check this, I
would be happy to do so.
> User forced to log in twice after checking WebClientInfo
> --------------------------------------------------------
>
> Key: WICKET-6929
> URL: https://issues.apache.org/jira/browse/WICKET-6929
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 9.5.0
> Environment: Windows 10 Enterprise, JDK 11.0.7, NetBeans 11.3 and
> Payara 5.201
> Reporter: Sushila Burgess
> Assignee: Sven Meier
> Priority: Minor
> Labels: WebClientInfo
> Attachments: icase_debug.zip
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
