Well, it does sound like you just need proxies for cluster-configs, TestCluster, etc... Your site is called opscenter and then you proxy a directory called opscenter. But the 2 have nothing to do with each other. Your site can be called opscenter and then you need a proxy for TestCluster, etc... You haven't proxied opscenter the host - you've proxied opscenter the directory. Because opscenter the host has many directories with names other than opscenter, you need to have proxy rules for all those too. Or, as I'd said, you may be better off using rewrite if there are proxies that proxy is not complicated enough for.
On Fri, Jun 19, 2015 at 3:15 AM, Jonathan Ballet <jbal...@gfproducts.ch> wrote: > Hi Spencer, > > I certainly know how to configure a proxy or how to rewrite URLs if I need > to and we are currently not looking for a contractor, but thanks for your > message! :) > > Jonathan > > > On 06/18/2015 11:29 AM, Spencer Brown wrote: > >> First, your firewall should really be your frontend There operational >> frontend is apache, which is common. You want every url with opscenter >> in it handled elsewhere. You could also set up proxies for /. >> cluster-configs, etc... >> Then there is mod_rewrite, which provides a lot more granularity about >> when you want what gets handled where.I set up the architectural >> infrastructure for Orbitz and some major banks, and I'd be happpy to >> help you out on this. I charge $30/hr., but what you need isn't very >> complex so we're really just talking $100. >> >> On Thu, Jun 18, 2015 at 5:13 AM, Jonathan Ballet <jbal...@gfproducts.ch >> <mailto:jbal...@gfproducts.ch>> wrote: >> >> Hi, >> >> I'm looking for information on how to correctly deploy an OpsCenter >> instance behind a HTTP(S) proxy. >> >> I have a running instance of OpsCenter 5.1 reachable at >> http://opscenter:8888/opscenter/ but I would like to be able to >> serve this kind of tool under a single hostname on HTTPS along with >> other tools of this kind, for easier convenience. >> >> I'm currently using Apache as my HTTP front-end and I tried this >> naive configuration: >> >> <VirtualHost *:80> >> ServerName tools >> ... >> ProxyPreserveHost On >> ######### Proxy to OpsCenter ######### >> ProxyPass /opscenter/ http://opscenter:8888/opscenter/ >> ProxyPassReverse /opscenter/ http://opscenter:8888/opscenter/ >> </VirtualHost> >> >> This doesn't quite work, as OpsCenter seem to also serve specific >> endpoints from / directly >> >> >> Of course, it doesn't correctly work, as OpsCenter seem to also >> serve specific data from / directly, such as: >> >> /cluster-configs >> /TestCluster >> /meta >> /rc >> /tcp >> >> Is there something I can configure in OpsCenter so that it serves >> these URLs from somewhere else, or a list of known URLs that I can >> remap on the proxy, or better yet, a known proxy configuration to >> put in front of OpsCenter? >> >> Regards, >> >> Jonathan >> >> >>
