Changes between Version 16 and Version 17 of Integrated Webserver

Timestamp:

Jul 26, 2015, 5:20:09 PM (9 years ago)

Author:

Christian Illy

Comment:

--

Integrated Webserver

@@ -3 +3 @@
 Meant to become an easy to use and everywhere accessible administration interface mostly for tasks like player management. (Currently in early development stage)
 
+
 == Current features ==
 * Viewing the map of the game as much as visited by players.
 
+
 == Access ==
+The webserver will listen on the port defined as ControlPanelPort (from serverconfig) + 2. I.e. if you have set ControlPanelPort to 8080 (as it is by default) the webserver will listen on ''!http://<yourIpOrDomain>:8082/''
 
-The webserver will listen on the port defined as ControlPanelPort (from serverconfig) + 2. I.e. if you have set ControlPanelPort to 8080 (as it is by default) the webserver will listen on ''!http://<yourIpOrDomain>:8082/''
 
 == Is it running? ==
@@ -16 +18 @@
 }}}
 If it does the server was started on the given port.
+
 
 == Permissions ==
@@ -33 +36 @@
  webpermission add webapi.getstats 1000
 
+
 == Web Tokens ==
 As tools like server managers obviously can not identify themselves with Steam login a token system has been added. That way those tools can provide a predefined token on ''each'' request to the webserver and those requests will be handled with the permission level given to that specific token. Web tokens are set up with the ''webtokens'' command.
+The tokens have to be passed to each request like this:
+ !http://<server>:<port>/map/0/2/1.png?'''adminuser=<tokenuserpart>&admintoken=<tokenpasswordpart>'''
+For example, if your server is running on your machine, port 8082 and you added a webtoken with name "admin" and password "supersecrettoken" a request would look like this:
+ !http://localhost:8082/api/getstats?adminuser=admin&admintoken=supersecrettoken
+
 
 == apache and mod_proxy ==