Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m using Wicket (6) for an webapplication. I’m a bit curious about Wicket’s default cookie-handling. What cookies are set per default? Does some components use cookies per default? What happens if the user doesn’t allow cookies, does the jSession in url happens instead? Is there an easy way of turning off all cookies in Wicket?
The only cookie Wicket uses is the standard jsessionid cookie provided by your container. And even that is optional when working in stateless pages.
It is impossible to say which components use cookies, as there are thousands, tens of thousands components and some of them might use cookies. The only components/behaviors that require a bound session are Ajax components and stateful components/behaviors.
That said, why are you so anxious about removing all cookies? If it is the new EU cookie law, then you can rest assured, cookies for the proper use of your application are permitted. Tracking users across websites that is prohibited without consent, not session cookies or other cookies that keep you logged in.