I also thought that Tomcat should take care of the redirect configured in web.xml by itself, but that does not seem to be the case. To me it seems like Tomcat does create its own redirect response, but that Tomcat still calls its filter chain, which will invoke my WicketFilter which leads to wicket also constructing a redirect, which I would guess takes precedence over the one created by Tomcat.
Using the debug tool in Google Chrome and FireBug in Firefox, I can affirm that the redirect really is a 302 redirect. Martin Grigorov-4 wrote: > > This looks wrong. It should be "../LoginPage" instead. > But I'm not sure that Wicket creates this redirect location. From the > description in your first mail I think the web container (Tomcat) > should care about the redirect. I.e. hitting an Url that requires > authentication Tomcat will not deliver it to WicketFilter at all but > will do the redirect to the 'form-login-page'. I'm not sure how > exactly the web container does this though... If it is redirect 302 > then all should be fine, but if it is RequestDispatcher.forward() then > Wicket will be confused indeed. See > https://issues.apache.org/jira/browse/WICKET-4138 > -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wrong-path-for-resources-on-redirected-login-page-tp3920038p3932467.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
