Let's say you have hundreds of Device Servers with embedded web servers, with each such Device Server providing access to a number of web pages. It is very easy to access every embedded Web Server when all of them have real static IP addresses. However, in real life, most Device Servers are installed in local networks protected by firewalls, and static IP addresses cost money. In this case, there is no way to access these Device Servers directly. The HTTP Proxy service solves this problem by providing a generic way to access all embedded web servers through Iotellect Server. It works like this:
A Device Server with an embedded web server connects to the Iotellect Server. Its account should be configured to use HTTP Proxy mode.
Someone wants to see the web pages from this particular Device Server, so they start a web browser and surf to a URL such as http://server.bigcompany.com/dev/admin/dev1/data.html
The HTTP request sent by a browser is received and processed by the Iotellect Server
Iotellect Server redirects the HTTP request to the admin.dev1 Device Server, to which it is currently connected.
The Device Server processes the request and sends the data.html page to the Iotellect Server.
Iotellect Server forwards this page to the browser.
