Web publishing Gemini through reverse proxy with port mapping
We have published our GEMINI website to the net. It is known on the company network with an internal hostname publishing on port 10080. It then goes through a reverse proxy and a firewall out to the www, where it is known with a public name x.y.z (the port translation 80<->10080 is done by the reverse proxy). In the general settings the enforce URL is set to http://x.y.z/gemini/. The site works partialy: the style sheets and toolbars fail to load (i.e. when trying to add a comment) because an URL in the form of "http://x.y.z:10080/GEMINI/js/..." is requested as something like "http://x.y.z/gemini/js/" is awaited.
To bypass the problem we have setup the reverse proxy to publish on the 10080 port, with the drawback that the firewall of some external users have that port closed.
Is there a configuration trick to solve that issue ?
User21703
· 1 |
|
Friday, July 8, 2011, 11:41:53 AM |