koa-generic-session

generic-session

Notice: koa-session support external store now, please migrate to koa-session.

Generic session middleware for koa, easy use with custom stores such as redis or mongo, supports defer session getter.

This middleware will only set a cookie when a session is manually set. Each time the session is modified (and only when the session is modified), it will reset the cookie and session.

You can use the rolling sessions that will reset the cookie and session for every request which touch the session. Save behavior can be overridden per request.

Usage

Example

var session = require('koa-generic-session');
var redisStore = require('koa-redis');
var koa = require('koa');

var app = koa();
app.keys = ['keys', 'keykeys'];
app.use(session({
  store: redisStore()
}));

app.use(function *() {
  switch (this.path) {
  case '/get':
    get.call(this);
    break;
  case '/remove':
    remove.call(this);
    break;
  case '/regenerate':
    yield regenerate.call(this);
    break;
  }
});

function get() {
  var session = this.session;
  session.count = session.count || 0;
  session.count++;
  this.body = session.count;
}

function remove() {
  this.session = null;
  this.body = 0;
}

function *regenerate() {
  get.call(this);
  yield this.regenerateSession();
  get.call(this);
}

app.listen(8080);

• After adding session middleware, you can use this.session to set or get the sessions.
• Setting this.session = null; will destroy this session.
• Altering this.session.cookie changes the cookie options of this user. Also you can use the cookie options in session the store. Use for example cookie.maxAge as the session store's ttl.
• Calling this.regenerateSession will destroy any existing session and generate a new, empty one in its place. The new session will have a different ID.
• Setting this.sessionSave = true will force saving the session regardless of any other options or conditions.
• Setting this.sessionSave = false will prevent saving the session regardless of any other options or conditions.

Options

• key: cookie name defaulting to koa.sid

• prefix: session prefix for store, defaulting to koa:sess:

• ttl: ttl is for sessionStore's expiration time. it is different with cookie.maxAge, default to null(means get ttl from cookie.maxAge).

• rolling: rolling session, always reset the cookie and sessions, defaults to false

• genSid: default sid was generated by uid2, you can pass a function to replace it

• defer: defers get session, only generate a session when you use it through var session = yield this.session;, defaults to false

• allowEmpty: allow generation of empty sessions

• errorHandler(err, type, ctx): Store.get and Store.set will throw in some situation, use errorHandle to handle these errors by yourself. Default will throw.

• reconnectTimeout: When store is disconnected, don't throw store unavailable error immediately, wait reconnectTimeout to reconnect, default is 10s.

• sessionIdStore: object with get, set, reset methods for passing session id throw requests.

• valid: valid(ctx, session), valid session value before use it

• beforeSave: beforeSave(ctx, session), hook before save session

• store: session store instance. It can be any Object that has the methods set, get, destroy like MemoryStore.

• cookie: session cookie settings, defaulting to

  {
    path: '/',
    httpOnly: true,
    maxAge: 24 * 60 * 60 * 1000 //one day in ms,
    rewrite: true,
    signed: true
  }
  

  For a full list of cookie options see expressjs/cookies.

  if you setcookie.maxAge to null, meaning no "expires" parameter is set so the cookie becomes a browser-session cookie. When the user closes the browser the cookie (and session) will be removed.

  Notice that ttl is different from cookie.maxAge, ttl set the expire time of sessionStore. So if you set cookie.maxAge = null, and ttl=ms('1d'), the session will expired after one day, but the cookie will destroy when the user closes the browser. And mostly you can just ignore options.ttl, koa-generic-session will parse cookie.maxAge as the tll.

Hooks

• valid(): valid session value before use it
• beforeSave(): hook before save session

Session Store

You can use any other store to replace the default MemoryStore, it just needs to follow this api:

• get(sid): get session object by sid
• set(sid, sess, ttl): set session object for sid, with a ttl (in ms)
• destroy(sid): destroy session for sid

the api needs to return a Promise, Thunk or generator.

And use these events to report the store's status.

• connect
• disconnect

Stores Presented

• koa-redis to store your session data with redis.
• koa-mysql-session to store your session data with MySQL.
• koa-generic-session-mongo to store your session data with MongoDB.
• koa-pg-session to store your session data with PostgreSQL.
• koa-generic-session-rethinkdb to store your session data with ReThinkDB.
• koa-sqlite3-session to store your session data with SQLite3.
• koa-generic-session-sequelize to store your session data with the Sequelize ORM.
• koa-generic-session-knex to store your session data with the Knex query builder.

Licences

(The MIT License)

Copyright (c) 2013 - 2016 dead-horse and other contributors

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.