changes related to client upgrade fixes

web/app/assets/javascripts/JamServer.js

@@ -357,7 +357,6 @@
         $self.triggerHandler(EVENTS.CONNECTION_UP);
 
         activeElementEvent("afterConnect", payload);
-        console.log('_DEBUG_ JamServer afterConnect', payload);
         if (payload.client_update && context.JK.ClientUpdateInstance) {
           context.JK.ClientUpdateInstance.runCheck(
             payload.client_update.product,
@@ -841,7 +840,7 @@
             : null, // latency tester doesn't have the stun class loaded
         };
         var uri = context.gon.websocket_gateway_uri + "?" + $.param(params); // Set in index.html.erb.
-        //console.log("_DEBUG_ connecting websocket: " + uri);
+        console.log("_DEBUG_ connecting websocket: " + uri);
 
         server.connecting = true;
         server.socket = new context.WebSocket(uri);

websocket-gateway/lib/jam_websockets/router.rb

@@ -996,6 +996,9 @@ module JamWebsockets
           end
         end
 
+        puts "========================="
+        puts "O/S = #{os}"
+        puts "========================="
         # if we have OS data, try to grab client update data and let the client have it
         update = ArtifactUpdate.find_client_by_os(os) if client_type == Connection::TYPE_CLIENT && os