Session checking stable, not sure how to test redirect, but clearing client cookie or deleting server session files now handled gracefully.

server.js

@@ -101,7 +101,19 @@ io.use(iosess(session));
 
 io.on('connection', function(socket){
     //winston.info('a user connected');
-    winston.info('sessio id, '+ socket.handshake.session.id);
+    winston.info('session id, '+ socket.handshake.session.id);
+    if (!socket.handshake.session.passport.user) {
+        // Send redirect to client, socket connection will close when client goes back to /login.
+        // But disconnect just in case client is misbehaving.
+        winston.info('Session DNE, redirect and disconnect.');
+        socket.emit('redirect', '/login');
+        socket.disconnect();
+    }
+    // next line works until container restarted...need to validate session existence?
+    // or is the problem with a nodemon restart???
+    winston.info('user id, '+ socket.handshake.session.passport.user);
+    // not sure if next line works yet...
+    //winston.info('user name, '+ socket.handshake.session.passport.user.username);
     fileSystem.readFile(notePath, {encoding: 'utf-8'}, function(err,data){
         if (!err){
             winston.info('file read on connection');

views/index.html

@@ -99,6 +99,9 @@
     });
 
     socket.on('conflict', function(msg){ alert(msg) });
+    socket.on('redirect', function(destination) {
+        window.location.href = destination;
+    });
 </script>
 </body>
 </html>