Closed jspdown closed 8 years ago
DEBUG= koa-redis node server
to see the debug info? I test in a simple example, and works fine.
Works for me too.
You can add console.log()
s inside your node_modules/koa-generic-session
.
when set rolling: true
the bug happened. If another request come follow the 'logout' request, the request followed will resave the session in the store.
When I unset rolling
, it works fine.
added some test cases for rolling session, anybody can reproduce the issue and create a test case?
https://github.com/koajs/generic-session/commit/0b1d52eb32aa0ace4c997277542decae4b07c2ec
The bug as raised by @miserylee is still there. How can we mitigate this issue if we need to use rolling:true for every request while making sure the session was destroyed if we call it to destroy?
Hi, I'm using
generic-session
withkoa-redis
on a side project and can't figure out how to destroy the session. I mean, I have a/logout
route that is suppose to destroy the current session with the following code:As mentioned in the README.md,
this.session = null
should destroy the session but in fact nothing happened. I put someconsole.log
in thedestroy
method ofkoa-redis
and I noticed this function was never called.FYI, modules versions are:
koa
: 1.1.2koa-generic-session
: 1.10.0koa-redis
: 1.0.1 And session are created bykoa-passport
(1.x.x)I try to
make test
inkoa-redis
andkoa-generic-session
and everything works as expected, 100% passed.