Express JS #13 - Sessions Pt. 1

Support the Channel:

Connect with me:

[xx-fwyq]

Probably the best video i've seen explaining this. Thanks a lot.

[danielouattara]

Thank you Anson for the material you provide to all of us.

In this course Anson artificially alters the session object in the index.js, at `app.get('/', ...)`, so that when he makes a request using development tools like `thunder client` or `postman`, the output of `console.log(req.sessionID)` will always be the same on any request. This tries to justify how applications sever can keep track of user for subsequent requests. Cool !

And the game is totally different on a real web browser: there, developers don't have to do anything on the session object and the sessionID value will remain the same. Am I wrong Anson ?

[hasibalfuad]

Great content. Can you please tell What is the theme and the font you are using?

[starrynight]

So in the real world development, we have to modify the session object manually to keep the sessionId to be same?

[abdullhaseeb]

for me without setting session.visited = true the session id is same, is that a problem?

[shakilthakur]

i don't understand how server will identify who the user is. i understand when user will first visit a website, server will send a session id to client and client will send the session in each subsequent request to server. but how server will recognize who the user actually is? what the role of the user, is he authenticated or not? i will appreciate the clarification. thank you.

[uni]

even with the visited set to true, its still generating new sessions for the same requests

[josephkoh]

hey anson i have a qn... So for example, when u visit the ecomm web app how does the app knows whether to render an admin login page or user login page? As i know usually there is a different login page based on the user role like admin and user

[echendukwe]

Hi, lovely video but i do get a cookies
error in production

[tarunkatal]

Slides are too fast in start.. o/w HQ content❤