I know, that this setting tells Wicket when to create the HttpSession. And it seems that if the HttpSession is created in the Https request, the created Session is not visible to any Http request. In Wicket 1.4 we never switch back to the Http protocol once the secure protocol is used. So probably this problem never occured. I try to use the listener to figure out what happens.
-- View this message in context: http://apache-wicket.1842946.n4.nabble.com/HttpsMapper-creates-HttpSession-by-default-tp4079305p4079409.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
