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:solomax...@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 <mika.tapanai...@digia.com<mailto: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 -- WBR Maxim aka solomax
