Skip to content

Client-side sessions versus server-side sessions #20

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

Open
toraritte opened this issue Jun 19, 2018 · 1 comment
Open

Client-side sessions versus server-side sessions #20

toraritte opened this issue Jun 19, 2018 · 1 comment

Comments

@toraritte
Copy link
Owner

toraritte commented Jun 19, 2018

To digest:
http://phillbarber.blogspot.com/2014/02/client-side-vs-server-side-session.html

(Related to #19 )

@toraritte
Copy link
Owner Author

Keep this in mind:

https://security.stackexchange.com/questions/115695/when-should-server-side-sessions-be-used-instead-of-client-side-sessions

Before you create client side sessions, you should ask yourself if you really need it (which may be the case if you have multiple servers which need to share the same session state, eg for scalability reasons). Session data is traditionally handled server side for a reason: It contains data that the client should not be able to read or change. That's easiest to do by just not sending it to the client.

Setting up a complex system to store session data client side is difficult, and a lot may go wrong doing it. If it's not necessary, just store the data server side.

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

No branches or pull requests

1 participant