-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add cookie check on edit #6
Comments
Using django session management. |
?elaborate the issue please |
What? Why session? Alternative |
Another thing is: |
why we are not using complete auth then... user will give permissions to others to collab...all its snippet will be saved under him ? |
I don't think user permission is necessary, it's apparent that user shared the url and is allowing people to edit (unless otherwise specified, we can make a checkbox for that). Also other users have to be logged in to edit too in this case. Complete auth seems totally unnecessary because a mere session can achieve the same thing. DB space is saved, faster db queries etc But I would like to hear reasons why complete auth is useful. |
Do you want to view all the old snippets for last one hour only ? |
Whatever you saw fit. :) |
okay i have initiated the session mechanism but what should the page display in old snippets |
Since we are not giving access via |
Checks on whether the same user is trying to edit the snippet.
The text was updated successfully, but these errors were encountered: