Re: Too many 302 redirects with 1.5.8 Wicket

Perfect, Martin. Thank you very much for tip, I will point my investigation in this way. cheers Tomas. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Too-many-302-redirects-with-1-5-8-Wicket-tp4674532p4674567.html Sent from the Users forum mailing list archive at

Re: Too many 302 redirects with 1.5.8 Wicket

On Thu, May 5, 2016 at 1:29 PM, tomask79 wrote: > Hi Martin, > > REDIRECT_TO_BUFFER and by is meant > >

Re: Too many 302 redirects with 1.5.8 Wicket

Hi Martin, REDIRECT_TO_BUFFER and by is meant

Re: Too many 302 redirects with 1.5.8 Wicket

Hi, What is in GET /wicket/page?420-1. ? Which render strategy do you use ? REDIRECT_TO_BUFFER (the default), REDIRECT_TO_RENDER or ONE_PASS_RENDER ?

Re: Too many 302 redirects with 1.5.8 Wicket

Well, today I found out we experience this problem also with Wicket 6.0...(6.21) Guys, do you have any idea when this could happen? When Wicket could rotate the same request over and over again? Pattern is still the same...POST -> and eventual 302 GET for response is rotated many

Re: Too many 302 redirects with 1.5.8 Wicket

There are no less than 7 newer versions of 1.5.x, so perhaps update to 1.5.15 to see if you're having better luck? According to the changelog, there were several redirect-related bugs fixed in 1.5.11: https://github.com/apache/wicket/blob/wicket-1.5.x/CHANGELOG-1.5#L41 Sincerely, Jeroen

Too many 302 redirects with 1.5.8 Wicket

Hi guys, currently in the older deployed versions of our system in the cluster environment, we're experiencing sometimes strange behaviour where one session loops in the 302 redirect cyclethis is the log from load balancer: "GET /wicket/page?420-1. 302 333 (redir=-,