gladiusio / gladius-masternode Goto Github PK

When a connection is received by the masternode, we need to determine the clients IP address which may be behind a proxy node.

First time the route is seen by the masternode

For all pages with linked assets, every supported asset's src / href attributes will be removed and a gladiusID attribute will be added, the page along with all of it's supported assets will be copied to the content nodes. The master node also stores the SHA256 of the stripped page and the assets for later verification.

When the page is loaded

The page is loaded in the browser by the masternode JS which verifies the hash of the incoming HTML. This then loads the various assets by their gladiusID attribute and also verifies their hash.

Other things to think about

Rendering the base64 encoded css from the content node before we render the rest of the page. This probably means that CSS will need to be specially added as a link by the masternode rather than it's html being loaded from the content node.

-Use geoip to lookup the closest nodes
-KD-trees in Go (thread safe)