Hi, I think the first approach is better. I'd just use JavaScript to check that the cookie is stored (and probably remove it) instead of doing http redirect. The second approach requires usage of org.apache.wicket.settings.IRequestCycleSettings#setGatherExtendedBrowserInfo(true)
On Thu, Apr 4, 2013 at 3:43 PM, divad91 <[email protected]> wrote: > Hi > > I just migrated to wicket 6.6.0 and I need display a page to the customer > when his browser cookies are disabled. > > Is there a better approach to do this ? Is it better to > > - add a cookie to the response and redirect to the same page and then check > the presence of the cookie in the request > > Or > > - use session().getClientInfo().getProperties().isCookiesEnabled() provided > method. > > Thanks. > David > > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Browser-Cookie-detection-tp4657744.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com <http://jweekend.com/>
