Hi wicketeers,
I was hoping to get rid of the jsessionid that appears in the
browsewr bar when running my wicket app under Tomcat 7, and I added the
following to web.xml:
<session-config>
<session-timeout>30</session-timeout>
<tracking-mode>COOKIE</tracking-mode>
</session-config>
However, now in production we get all these 302 redirects which are
causing an infinite recursion. What is the best way to handle this? I
also found a wiki page
https://cwiki.apache.org/confluence/display/WICKET/SEO+-+Search+Engine+Optimization
but wasn't sure if this also applied to using Wicket 6.
Thanks, Jason
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
