I just realized something that should maybe have been obvious to me at once... I'm not at home and able to test this atm, but I'm quite sure that my WicketFilter is positioned before my <security-constraint> in my web.xml. I didn't think <security-constraint> was treated as a filter, so I didn't think the placement of that section mattered. But if the order matters, I guess that would explain why WicketFilter is invoked even when I expected Tomcat to make a redirect.
If this is the cause of my problem I feel stupid... :) However, the same web.xml did work in wicket 1.4.18, probably due to lucky circumstances... -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wrong-path-for-resources-on-redirected-login-page-tp3920038p3932608.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]
