On 01.10.2012 15:02, Martijn Dashorst wrote:
But is it severe enough to hold back this release? If this bug hits you (and cookie-less operation is important) don't upgrade to 6.1, but wait for 6.2?
It's not limited to Wicket applications which don't use cookies. This always happens for the very first request when the container can't know whether the browser supports cookies or not (unless, of course, the container is configured not to do it).
Christoph
