Repository navigation
Request: Intro for beginners #188
Description
I'm a beginner and am not entirely sure what this is doing.
My understanding: if it's a "first time request", 1) create an empty session object and 2) send back a header to tell the browser to create a cookie. If it's a request with a cookie, somehow use the cookie to get the session.
When does the cookie go away? The session?
Activity
gabeio commentedon Jul 26, 2015
There is an example. If it's a first time request with
saveUninitialized: falseit will not create a session until the user is logged in or somehow been authorized. That is great for apps that have a lot of not logged in users browsing their pages or bots roaming around and they don't want those users to be using sessions. That also is especially good to comply with EU cookie privacy laws. The cookie has it's own settings cookie-options so you can decide how long it stays, cookiemaxage. The session can have a TTL (time to live) depending on the store (db-connection-library). For example, redis has TTL as a build in function so the session can have a TTL. Otherwise the session will live as long as your database is not changed.siddo420 commentedon Jan 16, 2016
can you also shed some light on httpOnly param please? For example, what are the pros and cons of setting it to false.
I need it set to false so I could read cookies from another window (iframe etc)
gabeio commentedon Jan 16, 2016
the httpOnly param is an http protocol function not ours see here for some info. But I can shed some light on it. So in essence it only will send the cookie over http(s) requests. By default (without httpOnly) the browser can and will share the cookies with javascript that is run on your website. This may or may not be ideal. It completely depends on your application. For most secure practice you want httpOnly set as you don't want anyone to be able to copy your cookies to someone else's browser or sent/saved to a different server.
mattxdonovan commentedon Oct 26, 2016
Should this be closed or is there something being requested?
k11k2 commentedon Jul 5, 2017
I want to set a session at server side
sessionStorage.setItem("mySession","This is mySession")and use to get over client side(angular 2) assessionStorage.getItem("mySession")Is it possible by using thisexpress-session? if so, how could I achieve it? @gabeio @dougwilsonreq.session.mySession = req.body.mySessionWhat it really does ? did it store as
sessionStorage.setItem("mySession","This is mySession")if so, how can i retrieve it with out knowing where it is stored. ? some one help me ! new to this phase.gabeio commentedon Jul 5, 2017
@AlwaysAbhl001 sessions are data which are connected to the client's browser in a way that prevents them from being able to tamper with the variables as they are not ever passed to the user.
If you wish for them to be able to grab certain variables from the server I might advise you look into normal signed cookies (depending on what the values are) but keep the master copy of that variable in the session data (basically do not ever read from the cookie on the server side).
The other option would be to have an API which allows certain predefined variables in their session to be accessed by angular (best option is read only if any) e.g.: /api/session/mySession would return just the variable's value.
Side-notes: It would be very bad to return the entire session object ever or allow the user to be able to plug any variable into the /api/session/ and get the whole variable by brute force.
k11k2 commentedon Jul 6, 2017
@gabeio
No Man, it a token I can't serve it on API. As mentioned here link, I did by using cookie but storing token at cookie is a bad practice so, searching for effective process.
joewagner commentedon Jul 6, 2017
@AlwaysAbhl001 This is an issue asking for an intro for beginners. Do you want to know best practices for sharing a token between the client and server? Have you looked at the csurf module?
Regardless, it seems like your questions are off topic for this issue