Hi Mika, I know for sure that proxying Openmeetings on the top of httpd_proxy is possible - we get it worked in some projects. Details are distributed over the mail list [1].
Thanks for your interest. [1] http://markmail.org/message/jxogln76gmncprq3 -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 [1] Start using Apache Openmeetings today, http://openmeetings.apache.org/ [2] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/ [3] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings On Mon, Jul 14, 2014 at 4:32 PM, Tapanainen Mika <mika.tapanai...@digia.com> wrote: > Hello, > > > > I’m testing OpenMeetings, which is installed behind the firewall. > > > > The public address of the OpenMeetings meeting is: > > > > <publicAddress>/openmeetings?invitationHash=xyz > > > > and this is redirected by the firewall etc. to the inner address: > > > > <innerAddress>/openmeetings?invitationHash=xyz > > > > This is not working and no page are loaded. There are error message: > > > > Hups! Google Chrome didn't find the address <innerAddress>. > > > > There are HTTP codes 304 and 204. Is it so that OpenMeetings tries to use > the innerAddress, but the browser can’t see it, because it is behind the > firewall? Is it so that OpenMeetings redirects to innerAddress and the > browser can’t see it? > > > > Is it possible to configure the OpenMeetings so that the redirects are for > the publicAddress? Or what is wrong in my situation? > > > > BR, > > > > Mika > >
