[ 
https://issues.apache.org/jira/browse/WICKET-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sven Meier resolved WICKET-6295.
--------------------------------
    Resolution: Fixed

I've backported parts of the changes from Wicket 7.x:
No redirect-loop should occur any longer

Note that if you click the continue link while the meta refresh is still 
loading, you'll end on the application's home page instead of the original 
destination.

This is inherent to the current implementation using an intercept page (on all 
branches): the meta refresh consumes the original destination :/.

> Clicking Link in BrowserInfoPage results in infinite request loop
> -----------------------------------------------------------------
>
>                 Key: WICKET-6295
>                 URL: https://issues.apache.org/jira/browse/WICKET-6295
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 6.25.0
>            Reporter: Daniel Radünz
>            Assignee: Sven Meier
>             Fix For: 6.26
>
>
> Clicking on the link in the BrowserInfoPage used to gather extended browser 
> information results in an infinite loop in which the browser is alternating 
> between sending several GET and POST request per second for the 
> BrowserInfoPage.
> Based on QuickStart with Wicket 6.25:
> {code:Java|title=WicketApplication.java}
> ...
>       @Override
>       public void init()
>       {
>               super.init();
>               getRequestCycleSettings().setGatherExtendedBrowserInfo(true);
>       }
> ...
> {code}
> {code:Java|title=Homapage.java}
> public class HomePage extends WebPage {
>       private static final long serialVersionUID = 1L;
>       public HomePage(final PageParameters parameters) {
>               super(parameters);
>               // Get ClientInfo for example to conditionally add components
>               // further down in the code
>               ClientInfo clientInfo = Session.get().getClientInfo();
>               // Run code that takes a few seconds, just long enough to allow
>               // an impatient user to click the link in the BrowserInfoPage
>               try {
>                       Thread.sleep(3000);
>               } catch (InterruptedException e) {
>               }
>               add(new Label("version", 
> getApplication().getFrameworkSettings().getVersion()));
>     }
> }
> {code}
> Wicket 7 does not exhibit this behavior. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to