Hi Alec, Ok.. so far for now: - with wicket 1.4 removing the jessionID from URL should do the trick. And AFAIK wicket 1.4 should not do any redirect after this. - with wicket 1.5 the jsessionID is gone, BUT wicket 1.5 will do some redirect from path/yourPage to path/yourPage?0 (0 or other - wicket page version)
Michael Am Samstag, den 14.07.2012, 14:47 -0600 schrieb Alec Swan: > Thanks Michael. I read the first link before and the only thing that I > didn't do (and probable cannot do) is make my pages stateless. > > As far as the second link to DisabledJSessionIDinUrlFilter.java, > doesn't it just strip off JSESSIONID from the URL? Is there something > that I missed? > > Thanks, > > Alec > > On Sat, Jul 14, 2012 at 2:38 PM, Michael Mosmann <mich...@mosmann.de> wrote: > > Maybe this will help > > > > https://cwiki.apache.org/WICKET/seo-search-engine-optimization.html > > > > Or try this one: > > > > https://github.com/michaelmosmann/wicket-praxis/blob/master/de.wicketpraxis--pom/webapp/src/main/java/de/wicketpraxis/web/thema/howto/servletfilter/DisabledJSessionIDinUrlFilter.java > > > > Michael mosmann > > > > -- > > Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. > > > > > > > > Alec Swan <alecs...@gmail.com> schrieb: > > > > Thanks Josh, I upgraded to Tomcat7 and was able to disable cookies as > > you suggested. It worked! This, however does not help me change 302 > > redirect to 200. > > > > Is there any way I can make /lrm/ms/oid/123 return 200 just like > > /lrm/network as explained in my original post? > > > > Thanks, > > > > Alec > > > > > > On Sat, Jul 14, 2012 at 12:36 PM, Josh Kamau <joshnet2...@gmail.com> wrote: > >> I read somewhere that : > >> > >> When its first time you are accessing a page, tomcat doesnt know if cookies > >> are supported.. so to be safe, it will embed the session id in the url. IF > >> you then access another page, this time round tomcat knows what kind of > >> browser its dealing with ... and if cookies are supported, it wont embed > >> the session id in the url but will put it in a cookie.. > >> > >> Now to tell tomcat to always use the cookies , you add > >> > >> <session-config> > >> <tracking-mode>COOKIE</tracking-mode> > >> </session-config> > >> > >> > >> In your web.xml file.. > >> > >> Cheers > >> Josh > >> > >> On Sat, Jul 14, 2012 at 8:30 PM, Alec Swan <alecs...@gmail.com> wrote: > >> > >>> Hello, > >>> > >>> While working on my previous problem I found out that when I do a GET > >>> to one of my bookmarkable pages, e.g. /lrm/ms/oid/123, I get a 302 > >>> redirect to /lrm/ms/oid/../../ms/oid/123.0;jsessionid=xxx. However, > >>> when I do a GET to /lrm/network I get a 200 response and jsessionid is > >>> set as a cookie in the response. > >>> > >>> /lrm/network is explicitly mounted as mountBookmarkablePage in > >>> Application.init(). We are using Tomcat 6.0 and Wicket 1.4.17. > >>> > >>> How can I make /lrm/ms/oid/123 return 200 just like /lrm/network? > >>> Should we somehow mountBookmarkablePage each such page which we have > >>> thousands of? Will upgrading to Wicket 1.5 help achieve this behavior? > >>> > >>> Thanks, > >>> > >>> Alec > >>> > >>>_____________________________________________ > > > >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >>> For additional commands, e-mail: users-h...@wicket.apache.org > >>> > >>> > > > > _____________________________________________ > > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
