We use the IP address ‘192.168.0.100’ for the reverse proxy server in our examples and 192.168.0.200 as the CloudShark IP address. Make sure you substitute your own IP address when setting this up for your environment.
An administrator may wish to use a reverse proxy as a front end to CloudShark. There are countless reasons to desire this: to aggregate HTTPS services, add proprietary authentication, load balancing, et cetera. CloudShark can be the target of a reverse proxy if it is hosted on the root URL of the site. This means that CloudShark could be mapped to http://proxy/ but not http://proxy/cloudshark/.
In the occasion that CloudShark needs to exist under the umbrella of a reverse proxy as a member of other URLs competing for the root URL, it is highly recommended that a virtual host be used to provide each service with its own unique root URL.
Apache 2 is a common piece of software used to implement a reverse proxy.
First, enable the proxy module in Apache2:
In your Apache configuration, add the following configuration:
ProxyRequests Off ProxyPass / http://cloudshark-appliance/ ProxyPassReverse / http://cloudshark-appliance/
Restart Apache to invoke the new configuration.