Re: wicket 302 redirect loop

Thanks Martin, Guess the tomcat people forgot to put that into 7.0.18 - I'm using 7.0.22 and still have the problem. On Fri, Nov 18, 2011 at 10:16 AM, Martin Grigorov wrote: > On Fri, Nov 18, 2011 at 11:10 AM, thomas willomitzer > wrote: > > Good question. I guess I'll ha

Re: wicket 302 redirect loop

nd? > > -igor > > On Thu, Nov 17, 2011 at 11:34 AM, thomas willomitzer > wrote: > > No I'm afraid ... just tried > > > > On Thu, Nov 17, 2011 at 8:19 PM, Igor Vaynberg >wrote: > > > >> would adding a bogus query param help there? so t

Re: wicket 302 redirect loop

No I'm afraid ... just tried On Thu, Nov 17, 2011 at 8:19 PM, Igor Vaynberg wrote: > would adding a bogus query param help there? so the url will look like > this: localhost/?1&bogus=1 > > -igor > > On Thu, Nov 17, 2011 at 10:21 AM, thomas willomitze

Re: Apache Wicket is a Flawed Framework

Ooohh... I better double check what I'm writing on this list, Since the FBI is around ... ;) On Thu, Nov 17, 2011 at 7:56 PM, Alex Objelean wrote: > This is not an april fool's day, it is just an opinion of an > http://www.linkedin.com/pub/eric-kizaki/30/2b1/1a4 inexperienced > developer . > Eric

Re: wicket 302 redirect loop

s we are passing the /?1 url through > servletresponse#encoderedirecturl() tomcat is responsible for > appending the JSESSIONID if its not yet available in a cookie... > > -igor > > On Thu, Nov 17, 2011 at 2:16 AM, thomas willomitzer wrote: > > Hi, > > > > Thanks fo

Re: wicket 302 redirect loop

be closer to the > source of the problem. > > Good luck! > Bertrand > > > On 16/11/2011 12:21 PM, thomas willomitzer wrote: > >> Hi, >> >> Thanks I checked but no getPageParameters() override ;) >> >> Regards >> Thomas >> >

Re: wicket 302 redirect loop

d to use my method to generate > a new PageParameters instance for a page but overriding the Page method > gave your result. > > It's worth a shot! > > Regards, > Bertrand > > > On 16/11/2011 11:40 AM, thomas willomitzer wrote: > >> Dear All, >> >

wicket 302 redirect loop

Dear All, I've managed to get the jsessionid appended correctly when requesting a page without cookies enabled (wicket 1.5.3, tomcat 7.0.22). I get curl -v --insecure https://localhost/ -> Location: https://localhost/?1 curl -v --insecure https://localhost/?1 -> Location: https://localhost/.;jses

Re: jsessionid not appended for stateful pages

Sorry ... wicket 1.5.3 On Wed, Nov 16, 2011 at 5:11 PM, thomas willomitzer wrote: > Martin, > > Upgrading to 1.5.2 and using tomcat 7.0.22 fixed my issue - now I get > > > Location: > https://localhost/.;jsessionid=176D66D946CA33F54798F8EE1863C475 > > Thanks > Tho

Re: jsessionid not appended for stateful pages

Martin, Upgrading to 1.5.2 and using tomcat 7.0.22 fixed my issue - now I get > Location: https://localhost/.;jsessionid=176D66D946CA33F54798F8EE1863C475 Thanks Thomas On Wed, Nov 16, 2011 at 3:09 PM, Martin Grigorov wrote: > On Wed, Nov 16, 2011 at 4:02 PM, thomas willomitzer wrote:

Re: jsessionid not appended for stateful pages

} sb.append(anchor); sb.append(query); return (sb.toString()); } Thanks Thomas On Wed, Nov 16, 2011 at 1:39 PM, Martin Grigorov wrote: > Hi, > > On Wed, Nov 16, 2011 at 2:29 PM, thomas willomitzer > wrote: > > Dear all, > > > >

jsessionid not appended for stateful pages

Dear all, I've spent quite a bit of time tracking down a problem I'm having using wicket and stateful pages. I've enabled the jsessionid url rewriting in tomcat (by simply using the default settings) but I get a redirect url without the jsessionid. I've traced into tomcat's Response.encodeUrl and