Re-saves whole session instead of touching it

[nkbt]

While debugging with DEBUG=express-session npm start getting this:

Mon, 10 Apr 2017 04:49:43 GMT express-session fetching pMzWWbqOQ42F-nvuiIkP77AdGqCsSe_e
Mon, 10 Apr 2017 04:49:44 GMT express-session session found
Mon, 10 Apr 2017 04:49:44 GMT express-session touching
awsClient.putItem { TableName: 'reef-sessions',
  Item:
   { id: { S: 'pMzWWbqOQ42F-nvuiIkP77AdGqCsSe_e' },
     expires: { N: '1493009384267' },
     content: { S: '{"cookie":{"originalMaxAge":null,"expires":null,"secure":false,"httpOnly":false,"path":"/"},"user":{"id":"GUEST_ID","username":"guest","firstName":"","lastName":"","company":"","phoneNumber":"","city":"","timezone":""},"lastModified":1491799784267}' } } }
Mon, 10 Apr 2017 04:49:44 GMT express-session split response
Mon, 10 Apr 2017 04:49:44 GMT express-session touched

Expected to run setExpires: (id, expires) function but running put: (id, expires, content) instead

[nkbt]

Currently quickly fixed in the app by actually touching session every time with touchAfter: -1.

    store: new DynamoStore({
      tableName: SESSION_STORE_TABLE_NAME,
      endpoint: SESSION_STORE_END_POINT,
      region: AWS_REGION,
      touchAfter: -1,
      log: message => log({message}),
      err: (message, error) => err({message, payload: {errors: [error]}})
    })

So apparently session is re-saved every time to keep lastModified. That means if you have several microservices working with this session - it is re-saved multiple times and overrides legit login info.

When session is just touched - everything is fine.