When Nodejs is deployed on the same server and running two or more servers at the same time, a service user is logged on to squeeze out another user's problem

Problem Description: A server, the deployment of two or more different Web services, service a users after landing, service B users also logged in, when the user of service a click on the page, will return to the landing page.

The root of the problem: the browser saves the same session, the same cookie

Workaround:

App.use (Expresssession ({    secret: ' Keyboard Cat ',    resave:false,    saveuninitialized:true,    name: ' AAA '//The name here is worth the name of the cookie, the name of the default cookie is: Connect.sid});

Because the default cookie name is ' Connect.sid ', if you do not make a change, the user of the above service A will be squeezed out of User B, set the session name value in App.js.

When Nodejs is deployed on the same server and running two or more servers at the same time, a service user is logged on to squeeze out another user's problem