Secure URLs

In addition to rewriting “http://” links as described above, you can also use HyperGate with “https://” links.  You can even use HyperGate to secure your data without an SSL web server.

If you are currently transporting documents using “https” URLs, then you can enable AES and SSL compatability by changing the URL as follows:

Original SSL URL:

https://server_n[:server_p]/pathname

HyperGate Secure URL:

http://hgc_n:hgc_p/hgs_n:[hgs_p]s;[server_n[:server_p];]pathname

Note that the “s” is moved from the “http” to just after the HGserver port field.  This option causes HyperGate to protect your data using AES while it is in transit on the network, and to connect to the HTTP server using SSL.

For example, if the original or direct URL were:

https://www.abccompany.com/documents/bigfile.dat

the HyperGate URL (assuming default on-CPU installation) would be:

http://127.0.0.1:8088/www.abccompany.com:s;documents/bigfile.dat

Even if you don’t have an SSL server, HyperGate can still protect your data while it is in transit across the network.  To enable AES encryption with a non-SSL HTTP server, use “a”  in place of “s”.

For example, if the original or direct URL were:

http://www.abccompany.com/documents/bigfile.dat

then the following URL would provide AES protection for the same document:

http://127.0.0.1:8088/www.abccompany.com:a;documents/bigfile.dat