title: Node.JS server, WebSockets and HTTP vs HTTPS
body: <p>I am teaching myself Javascript and am working on a Node.JS app which runs on a users machine, reads and processes data from a locally running game and outputs it over a WebSocket to an HTML based front end. Its early days but I have the basics working and feel like I am learning a lot. </p>
  
  <p>My project so far is working fine when my front end is connecting to a WebSocket on the local machine (ws://127.0.0.1:8080).</p>
  
  <p>However I would like to be able to use other devices (within the local network) to view the same source of data, which causes a problem. When I change the WebSocket URL to the specific IP of the machine running the Node.JS app Chrome will no longer connect as my font end is served over HTTPS and this is an insecure WebSocket connection. (This does still work if I access the front end by opening the local .HTML file instead of viewing the served version, but this is not a real solution)</p>
  
  <p>At the moment, this project is just for me but I would eventually like to make a simple .exe of my app available to others which (correct me if I am wrong) rules out using a secure WebSocket connection, as I would have to somehow certify each individual machine using the app. </p>
  
  <p>As far as I can see, my only option is as to serve the page over HTTP instead of HTTPS and live with the insecure connection message. I don't have a particular problem with this, but am concerned that the goalposts relating to HTTP/HTTP will be moved in the future. </p>
  
  <p>So, is it OK to use HTTP only now? is there another solution that I am missing here or are one of my previous assumptions incorrect?</p>