-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Session cookies #6
Comments
Hi Micheal, That's correct the gem wipes out both session and persistent cookies that are stored by the app. It uses middleware variable to allow all or no cookies. Now, the EU directive since this gem has been written has changed and allows for storing of different session data like shopping carts, please see . The question now is what can be done to account for this change, one thought would be to allow a whitelist of session cookies to allow for storing necessary info if the user doesn't agree with storage of all cookies. Do you have any thoughts on api part of it? What rack app are you using? I'm happy to work with you on that. |
Hi Peter, thanks for the response. Although happy to help, I have to say I am a novice when it comes to cookies, sessions, and rack, which is why I was so pleased to see the gem in the first place! But happy to be involved in any testing you need. |
a whitelist of cookie names sounds good to me |
This is great. Although I have a question about session cookies, and please excuse my naivety on the workings of cookies and sessions.
The gem stops the saving of cookies - perfect.
But it also stops the use of session cookies, and I want to save a session cookie to say do not keep showing the message to opt out of the cookie .... Does the EU directive cover session cookies, and should they be allowed?
The text was updated successfully, but these errors were encountered: