'session' is undefined when using express / redis for session store

Question

I'm trying to use redis for sessions in my express app.

I do the following:

var express = require('express');
var RedisStore = require('connect-redis')(express);

app.configure('development', function(){     
    app.use(express.session({ secret: "password", 
                            store: new RedisStore({
                                          host: "127.0.0.1",
                                          port: "6379",
                                          db: "mydb"
                                        })  
          }));

Later on, in my app, if i do something like:

var whatever = req.session.someProperty;

I get:

Cannot read property 'someProperty' of undefined

This indicates that req.session is undefined (I can see this from a console.log entry in my config section)

I've definitely got redis running, and can see my app connects to it initially (using redis-cli monitor)

score 53 · Answer 1 · answered Apr 20 '12 at 01:43

53

Sessions won't work unless you have these 3 in this order:

app.use(express.cookieParser());
app.use(express.session());
app.use(app.router);

I'm not sure if router is mandatory to use sessions, but it breaks them if it's placed before them.

answered Apr 20 '12 at 01:43

Yxven

641
5
3

7

I had app.use(app.router); before express.session, which seems to break it. – 0x6A75616E Jun 01 '12 at 04:50
2

this answer was hard to find, should be somewhere in the docs. Upvoted! – ndequeker Aug 27 '12 at 14:18
1

This answer is more complete. You need to do both things: 1) enable cookieParser() and 2) move 'app.use(app.router);' to the bottom. I think this should be the correct answer. – Diego Pino Feb 21 '13 at 18:22
4

even with all 3 things in right order,req.session still undefined, do not know why. – ZHAO Xudong Jun 02 '13 at 00:32
Sir, I wish i could give you +2. You solved a TON of my problems – Cmag Dec 03 '13 at 16:32
Cheers.. !! Feeling nice to fix this. – Siten Feb 22 '16 at 12:13
2

How would this answer update since version 1.5.0? Currently, express-session is a separate module. According to the docs, "the cookie-parser middleware no longer needs to be used for this module to work" – Daniel Reina Mar 11 '17 at 17:35
I'm afraid I have to let someone else answer that. I abandoned node 5 years ago. – Yxven Mar 27 '17 at 16:15

JohnnyHK · Accepted Answer · 2012-12-22T15:16:59.543

10

Looks like you're missing:

app.use(express.cookieParser());

before your app.use(express.session(...)); call.

See here.

edited Dec 22 '12 at 15:16

answered Apr 17 '12 at 13:01

JohnnyHK

305,182
66
621
471

I'm having the same problem, but I do have app.user(cookieParser()) thing – Herokiller Dec 13 '15 at 13:55

score 4 · Answer 3 · answered Mar 08 '14 at 11:06

Had the same problem, however it was caused by changes in the latest version of express.

You now need to pass express-session to the function connect-redis exports to extend session.Store:

var express = require('express');
var session = require('express-session')
var RedisStore = require('connect-redis')(session);

score 4 · Answer 4 · answered Apr 11 '14 at 09:34

4

Things have changed recently with Express 3 / Express 4. Please confirm you are using version 4.

The complete middleware concept changed. You need to install these middlewares manually. "express-session" is one of the 4.0 middlewares.

I recommend to read

http://scotch.io/bar-talk/expressjs-4-0-new-features-and-upgrading-from-3-0 and https://github.com/visionmedia/express/wiki/Migrating-from-3.x-to-4.x

Additionally some users were confused that the github repo itself is named just "session" but

npm install express-session

is correct.

answered Apr 11 '14 at 09:34

sebilasse

4,278
2
37
36

1

This question was asked Apr 17 2012, therefore NOT related to version 4 – Alex Apr 11 '14 at 09:56
For version 4: https://stackoverflow.com/questions/31611920/session-using-nodejs-and-express-4-x-req-session-undefined – NBTX Jun 17 '17 at 09:35

score 2 · Answer 5 · answered Sep 30 '13 at 21:41

2

I had the same problem. It turned out that redis was simply configured to a different port.

answered Sep 30 '13 at 21:41

kaore

1,288
9
14

Thanks for putting me on the right track. I tripped over the fact that Heroku changed the REDIS_URL that I was using on my localhost. I could have known this as they mention this themselves: > "the REDIS config vars may change at any time. Relying on the config var outside of your Heroku app may result in you having to re-copy the value if it changes" https://devcenter.heroku.com/articles/heroku-redis#create-a-new-instance – Christiaan Westerbeek Jun 05 '19 at 09:24

'session' is undefined when using express / redis for session store

5 Answers5

Linked

Related