Hi, we also just experienced issues with this, and the fix of WICKET-2600 still causes problems (as already described in this post):
For the redirect to "." tomcat produces a Location header like http://www.example.org/. (notice the trailing dot), which causes IE to do request exactly this url, for which no page ist mounted. Therefore the 404 page not found. Is there a special reason why "." was chosen here? What do you think about an alternative handling like this: if (redirectUrl.startsWith("./")) { if (redirectUrl.length() == 2)) { WebRequest request = (WebRequest) requestCycle.getRequest(); String contextPath = request.getHttpServletRequest().getContextPath(); // e.g. "/myapp" String servletPath = request.getServletPath(); // e.g. "/" redirectUrl = contextPath + servletPath; } else { redirectUrl.substring( 2 ) } } Cheers, Martin On Sat, 2010-05-01 at 10:47 +0200, Erik van Oosten wrote: > This might be related to https://issues.apache.org/jira/browse/WICKET-2600? > > Regards, > Erik. > > > Op 29-04-10 16:57, Jimi wrote: > > I would also like to know if there is any solution (bug fix or workaround) > > to > > this bug. Currently each time a IE-user logs out from my web application he > > gets this ugly 404-error page, stating "The requested resource (/.) is not > > available". > > > > I use Wicket 1.4.7 and the web application is deployed as ROOT context on > > Tomcat 6.0.26. > > > > Is there no solution for this? > > > > Regards > > /Jimi > > > > -- Martin Grotzke http://www.javakaffee.de/blog/
signature.asc
Description: This is a digitally signed message part
