This setting is to tell Wicket whether to create a http session before
going https.
Otherwise if there is no http session until now and you create it in
https request then this session wont be visible to any http request.
Setting it to false wont bind the Session (i.e. wont create http session).
Register SessingBindingListener in web.xml and put a breakpoint in it
to see where is created the session.
On Thu, Nov 17, 2011 at 10:44 AM, Dirk Forchel <dirk.forc...@exedio.com> wrote:
> I'm not sure. But this is the comment within the source of the
> HttpsConfig.class:
>
> /**
> * Sets whether or not a new session is created before redirecting from
> {@code http} to {@code
> * https}
> * <p>
> * BE VERY CAREFUL WHEN SETTING THIS VALUE TO {@code false}.
> *
> * If set to {@code false} it is possible that the session created
> when in
> {@code https} pages
> * will not be accessible to {@code http} pages, and so you may end up
> with
> two sessions per
> * user both potentially containing different login information.
> * </p>
> *
> * @param preferStateful
> */
> public void setPreferStateful(boolean preferStateful)
> {
> this.preferStateful = preferStateful;
> }
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/HttpsMapper-creates-HttpSession-by-default-tp4079305p4079330.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
>
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
