Reverse Proxy with SSL support, Generated client Configs, JWT client to server auth, closes #13

public/static/js/kickwebsocket-manual.js

@@ -0,0 +1,26 @@
+//This is the basic template used to generate the kickwebsocket.  If needed you can manually edit this one to your needs and replace kickwebsocket-generated.
+
+IP = "192.168.1.100"
+Port = "8000"
+ClientAuthString = "" //String generated on first start and stored in the root as "clientAuth.txt" 
+
+//var ws = new WebSocket(`ws://${IP}:${Port}/websocket`); //for websockets not over an SSL reverse proxy
+
+//var ws = new WebSocket("wss://yoursubdomain.domain.org/subroute/") //for websockets behind an SSL reverse proxy
+
+var authMessage = {
+    MessageType: "authRequest",
+    Payload: [ClientAuthString]
+}
+
+var kickStart = {
+    MessageType: "torrentListRequest"
+}
+
+ws.onopen = function()
+{ 
+   ws.send(JSON.stringify(authMessage));
+   console.log("Sending authentication message...", JSON.stringify(authMessage))
+   ws.send(JSON.stringify(kickStart)); //sending out the first ping
+   console.log("Kicking off websocket to server.....", JSON.stringify(kickStart))
+};

public/static/js/kickwebsocket.js

@@ -1,12 +0,0 @@
-var ws = new WebSocket("ws://192.168.1.141:8000/websocket"); //creating websocket
-
-var kickStart = {
-    MessageType: "torrentListRequest"
-}
-
-ws.onopen = function()
-{
-   
-   ws.send(JSON.stringify(kickStart)); //sending out the first ping
-   console.log("Kicking off websocket to server.....", JSON.stringify(kickStart))
-};