For security reasons we've added a filter to our web application which
invalidates session if the session ID is exposed in the URL (disable
JSessionID URL encoding). We only accept HttpSession creation if the user
allows cookies. But this may be a problem for web crawlers (e.g. Google
bot), as they do not use cookies.
With Wicket 6.7.0 we did not have any problem as no page version has been
added to bookmarkable URLs by default (no redirect) as long as no form
submits occured. Which is sufficient because web crawlers can index the
site. After upgrading to Wicket 6.8.0 the page version number is added for
each bookmarkable page request and we can not display any page if cookies
and Javascript are deactivated in the browser. This results in an endless
loop ("The page isn't redirecting properly Firefox has detected that the
server is redirecting the request for this address in a way that will never
complete."). What causes the new behavior? What has been changed? I reckon
this relies to bug https://issues.apache.org/jira/browse/WICKET-5164. The
only solution I can think of, is to change the render strategy to
REDIRECT_TO_RENDER, as we've had the same problem with Wicket 1.5.x.
Or is there anything else I'm not being aware of?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/REDIRECT-TO-BUFFER-render-strategy-and-Wicket-6-8-0-tp4658991.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
