Yep. Depending on your renderStrategy (which by default is REDIRECT_TO_BUFFER), Wicket issues redirects (HttpServletResponse#sendRedirect), which are typically (or always?) translated to 302s by the servlet container.
Eelco On 5/25/07, Sean Sullivan <[EMAIL PROTECTED]> wrote: > > Question: > > Is Wicket setting the 302 response code for these HTTP requests? I am > seeing the 302 status code in all responses. (302 == > SC_MOVED_TEMPORARILY) > > Sean > > > > On 5/25/07, Sean Sullivan <[EMAIL PROTECTED]> wrote: > > > > > > Ok, I made the change to "home/" but I'm still having the same problem. > > > > I am unable to visit the application homepage: > http://dev.foobar.com/wicketdemo/home > > > > I've also tried http://dev.foobar.com/wicketdemo/home/ > (trailing slash) but it yields the same result. > > > > I think that I am experiencing a Websphere specific bug. The WAR runs > fine in Apache Tomcat 5.5.17 > > > > Sean > > > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
