You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Tapanainen Mika <Mi...@digia.com> on 2014/07/14 14:32:36 UTC
Wrong redirect behind the firewall? How to configure?
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
Re: Wrong redirect behind the firewall? How to configure?
Posted by Maxim Solodovnik <so...@gmail.com>.
if you need openmeetings2/ context work
you need additionally rename webapps/openmeetings folder to
be openmeetings2/
On 14 July 2014 20:45, Tapanainen Mika <Mi...@digia.com> wrote:
> Hello,
>
>
>
> I first tested this locally.
>
>
>
> Locally I changed the option application.base.url to
>
>
>
> http://localhost:5080/openmeetings2/
>
>
>
> and rebooted, but it is not working in the new address. Only in the old
> address.
>
>
>
> What I should do?
>
>
>
> BR,
>
>
>
> Mika
>
> *From:* Maxim Solodovnik [mailto:solomax666@gmail.com]
> *Sent:* 14. heinäkuuta 2014 15:49
> *To:* Openmeetings user-list
> *Subject:* Re: Wrong redirect behind the firewall? How to configure?
>
>
>
> you need to set configuration option: application.base.url (or something
> like this)
>
> if it doesn't help could you please provide steps to reproduce
>
>
>
> On 14 July 2014 19:32, Tapanainen Mika <Mi...@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
>
>
>
>
>
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
RE: Wrong redirect behind the firewall? How to configure?
Posted by Tapanainen Mika <Mi...@digia.com>.
Hello,
I first tested this locally.
Locally I changed the option application.base.url to
http://localhost:5080/openmeetings2/
and rebooted, but it is not working in the new address. Only in the old address.
What I should do?
BR,
Mika
From: Maxim Solodovnik [mailto:solomax666@gmail.com]
Sent: 14. heinäkuuta 2014 15:49
To: Openmeetings user-list
Subject: Re: Wrong redirect behind the firewall? How to configure?
you need to set configuration option: application.base.url (or something like this)
if it doesn't help could you please provide steps to reproduce
On 14 July 2014 19:32, Tapanainen Mika <Mi...@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
--
WBR
Maxim aka solomax
Re: Wrong redirect behind the firewall? How to configure?
Posted by Maxim Solodovnik <so...@gmail.com>.
you need to set configuration option: application.base.url (or something
like this)
if it doesn't help could you please provide steps to reproduce
On 14 July 2014 19:32, Tapanainen Mika <Mi...@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
>
>
>
--
WBR
Maxim aka solomax
Re: Wrong redirect behind the firewall? How to configure?
Posted by Alexei Fedotov <al...@gmail.com>.
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
<Mi...@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
>
>