Monday, 24 April 2017

Do we need cookieParser, session in Sails API only application?

Recently i deployed my SailsJS application in production mode and i got the following warnings.

memory, and will not scale past a single process.
Warning: connect.session() MemoryStore is not
designed for a production environment, as it will leak

I got solution for this problem here to use Redis for Session management.

But My Sails application serves only API and uses JWT token.

Still i need to use session and redis?

also i see the following default lines in my config/http.js file

// order: [
//   'startRequestTimer',
//   'cookieParser',
//   'session',
//   'myRequestLogger',
//   'bodyParser',
//   'handleBodyParserError',
//   'compress',
//   'methodOverride',
//   'poweredBy',
//   '$custom',
//   'router',
//   'www',
//   'favicon',
//   '404',
//   '500'
// ],

it's safe to remove the cookieParser and session from here?



via Raj Adroit

No comments:

Post a Comment