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 ?
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.
@@hugosenee2504 just put your code that related to session at chatgpt and tell it why its still generate a new session even though the visited set to true and make an explanation about it. ChatGPT is my best friend lol.
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
Usually you'd setup roles for a user on the server side, and the client side will see the roles property when the user data is fetched. If the user is trying to visit an admin page or restricted page, you want to check if they have the correct role first before granting access.
![[DRAGON BALL LEGENDS REVEALS ＆ STUFF] LEGENDS FESTIVAL 2024 Special Edition Part 1](http://i.ytimg.com/vi/mV5bGIswTtQ/mqdefault.jpg)
Probably the best video i've seen explaining this. Thanks a lot.
Best tutorial.
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 ?
Great content. Can you please tell What is the theme and the font you are using?
i think it is monolisa, u can use cascade mono as it is free
thank you very much
So in the real world development, we have to modify the session object manually to keep the sessionId to be same?
for me without setting session.visited = true the session id is same , is that a problem?
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.
even with the visited set to true , its still generating new sessions for the same requests
Check your Session config again.
@@ansonthedev i fixed it . thanks
Hi ! I have the same problem, can you tell me how did you fix it please ?
@@hugosenee2504 just put your code that related to session at chatgpt and tell it why its still generate a new session even though the visited set to true and make an explanation about it. ChatGPT is my best friend lol.
@@uni8380 how did you fix it please.
excellent
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
Usually you'd setup roles for a user on the server side, and the client side will see the roles property when the user data is fetched. If the user is trying to visit an admin page or restricted page, you want to check if they have the correct role first before granting access.
Hi, lovely video but i do get a cookies
error in production
I don't know how to help you if you don't provide the error you have.
Slides are too fast in start.. o/w HQ content❤