[jira] [Comment Edited] (WICKET-6929) User forced to log in twice after checking WebClientInfo

["Sven Meier (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17439366#comment-17439366 ] 

Sven Meier edited comment on WICKET-6929 at 11/5/21, 4:22 PM:
--------------------------------------------------------------

Found the reason:

On the BrowserInfoPage *Chrome* sends both request for the refresh-meta-header  *and* the onload-form-submit.

This triggers #continueToOriginalDestination() *twice*, which leads to the user being redirected to the homepage ... which in your application is the LoginPage :(.

So the fix for your problem is to change your homepage:

@Override
 public Class<? extends WebPage> getHomePage()

{    return WelcomePage.class; }

The LoginPage is *not* your homepage.


was (Author: svenmeier):
Found the reason:

On the BrowserInfoPage Chrome sends both request for the refresh-meta-header  *and* the onload-form-submit.

This triggers #continueToOriginalDestination() *twice*, which leads to the user being redirected to the homepage ... which in your application is the LoginPage :(.

So the fix for your problem is to change your homepage:

@Override
 public Class<? extends WebPage> getHomePage()
 {
   return WelcomePage.class;
 }

The LoginPage is *not* your homepage.

> 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
>            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.3.4#803005)