I think the reason may be that Jetty does not keep consistent behavior with the _dispatch property in the FormAuthenticator. After the successful authentication, the jetty always use redirect action, while in the other places of the class, it takes different actions depending on the _dispatch behavior. In Geronimo console, the value of _dispatch is true, so it forwards to the login page, and redirect after the successful authentication, I guess that it also depends on how the browser handle the redirect, maybe if it found the current ulr is the same with the redirect url, it ignores the request ??? I would like to set this value with false in Geronimo, or shall we open a bug in Jetty community ?
2009/7/28 Jarek Gawor <[email protected]> > Yes. I think that's exactly the same thing that causes the > console-testsuite to fail once in a while on Jetty. I thought it was > some selenium issue but since you ran into it outside of selenium, > it's probably some problem in Jetty. > > Jarek > > On Tue, Jul 28, 2009 at 11:22 AM, Ivan<[email protected]> wrote: > > I found some strange behavior about the Jetty admin console, sometimes, > > while I input the user name and password in the login page, then click > the > > login button, then after the refresh, the page still stays on the login > > page. So, I refresh the page again, get the welcome page. > > Does anyone encounter it too ? > > -- > > Ivan > > > -- Ivan
