Yes, that is all understood. However, since Servlet 3.0 you can switch-off
url rewriting for session ids using the tracking mode setting. And redirect
to buffer is the default wicket strategy. It might not be clear to most
wicket users that these two features together can lead to the endless
Hi,
Technically, this is not managed by Wicket.
It is the web container (like Tomcat, Jetty, ...) that deals with these
matters.
Wicket just tries to bind a HttpSession and cannot find it after the
redirect.
There could be many reasons for this. The most common one is that the
session has just
Hi,
when I select COOKIE in the web.xml and
disable cookies in the browser, I run into endless redirects for buffered
responses. You can see this behavior, e.g., in the forminput example of the
wicket-examples project.
Not sure, whether this is a bug. After all, how should wicket know that the
