Dear OpenMeetings Developers and Maxim,

 Maxim: I'm afraid you have problems with your reverse proxy server.

To further strengthen the foundation of OM 3.1.0 release, we did additional tests of ‘URL-in-browser’ by removing reverse proxy server. We directly accessed 3.1.0 from router through 5080 port number.

The ‘URLs-in-browser' test cases FAIL in this environment: CentOS 6.5, MySQL, Java 1.7.0_u67. Surprisingly, screensharing feature works. All the other features also work seamlessly.

Is there something we need to change in CXF API configuration for screensharing ‘URLs-in-browser' test to work in OM 3.1.0? So that the URLs in browser behave as expected: URL 1 goes to the /screenshare folder and URL 2 downloads the screenshare JAR file.

Test case results:

These URLs in browser bring back the signin page.

http://<Our_FQDN>:5080/openmeetings/screenshare <http://%3cOur_FQDN%3e:5080/openmeetings/screenshare>

http://<Our_FQDN>:5080/openmeetings/screenshare/openmeetings-screenshare-3.1.0-SNAPSHOT.jar <http://%3cOur_FQDN%3e:5080/openmeetings/screenshare/openmeetings-screenshare-3.1.0-SNAPSHOT.jar>

Thank you.
Sincerely,

Susheel Jalali
Coscend Communications Solutions
www.Coscend.com
----------------------------------------------------------------
CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail Messages from Coscend Communications Solutions' posted at: http://www.Coscend.com/Terms_and_Conditions.html


Reply via email to