-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Removed extra /logout handler #254
Conversation
Why delete this one? The other one does less error handling. |
Logout shouldn't fail. This one silently succeeds always and I believe that to be the correct approach. |
No the other one doesn't silently succeed if, for example, the database can't be reached. |
@gfosco updated the pull request. |
Cool. I would like to see some tests for this one as it's a security issue. (imagine a user logs thinks they have logged out from a public computer, but really the next person to use the computer can still log in as them) Hopefully we can avoid having to make any CVEs for quite awhile :) |
@gfosco updated the pull request. |
Yay passing tests! |
We're observing this code now always deleting the most recently created _Session. How do we call Parse.User.logout() and specify which session we want to delete? |
@woodardj were you able to figure it out? I'm having the same problem |
No description provided.