Skip to content
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

Persist session ID to identify owners of anonymously created compositions #52

Open
cheshire137 opened this issue Mar 8, 2017 · 0 comments
Labels
RQ06 User signup not required

Comments

@cheshire137
Copy link
Owner

When I check the Application > Cookies view in Chrome's web inspector for the app, I see a session cookie from Rails whose expiry time is "Session." "Session" cookies are handled differently by browser, and Chrome will keep your session cookies around, as I understand it, if the user has selected the "Continue where you left off" Chrome browser setting. I don't think we want to depend on this, as per RQ06, to hook up a bunch of ownerless compositions records if a user who has been using the site anonymously decides to sign up.

http://stackoverflow.com/a/1232231 looks relevant for modifying how long a Rails session cookie lasts. I'm not sure if that will be a rolling expiration date, like if we set it for a year in the future and the user uses the app again after 364 days, will the new expiration date be another year beyond that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RQ06 User signup not required
Projects
None yet
Development

No branches or pull requests

1 participant