Return-Path:
X-Original-To: apmail-openmeetings-commits-archive@www.apache.org
Delivered-To: apmail-openmeetings-commits-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
by minotaur.apache.org (Postfix) with SMTP id D3664E0DC
for ;
Thu, 7 Feb 2013 19:35:12 +0000 (UTC)
Received: (qmail 77474 invoked by uid 500); 7 Feb 2013 19:35:12 -0000
Delivered-To: apmail-openmeetings-commits-archive@openmeetings.apache.org
Received: (qmail 77451 invoked by uid 500); 7 Feb 2013 19:35:12 -0000
Mailing-List: contact commits-help@openmeetings.apache.org; run by ezmlm
Precedence: bulk
List-Help:
List-Unsubscribe:
List-Post:
List-Id:
Reply-To: dev@openmeetings.apache.org
Delivered-To: mailing list commits@openmeetings.apache.org
Received: (qmail 77444 invoked by uid 500); 7 Feb 2013 19:35:12 -0000
Delivered-To: apmail-incubator-openmeetings-commits@incubator.apache.org
Received: (qmail 77440 invoked by uid 99); 7 Feb 2013 19:35:12 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2013 19:35:12 +0000
Date: Thu, 7 Feb 2013 19:35:12 +0000 (UTC)
From: "Guillaume Rembert (JIRA)"
To: openmeetings-commits@incubator.apache.org
Message-ID:
In-Reply-To:
References:
Subject: [jira] [Updated] (OPENMEETINGS-431) OpenMeetings behind a proxy
doesn't work for screen sharing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
[ https://issues.apache.org/jira/browse/OPENMEETINGS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Rembert updated OPENMEETINGS-431:
-------------------------------------------
Description:
First, thanks Maxim for your answer and sorry to re-open it, I used a newer version - 2.1.0.r1428678-04-01-2013 and still have some issues (not the latest, I just tried to upgrade, but it failed to start and I got many error messages), so maybe it is already fixed. Just to explain the configuration better:
Public IPv4 Network - Forwarded Ports : 443/https to Machine 1 + 8088/rtmpT to Machine 2
Machine 1 : Apache Server https over 443 / proxy to Machine 2 clear http
Machine 2 : OpenMeetings Server - configuration: http over 5080 + rtmpT over 8088
Everything works fine here except the part where you click on share screen, you download public_9.njlp and execute it in javaws.
I get the following error:
com.sun.deploy.net.FailedDownloadException: Unable to load resource: http://meeting.myorganisation.com:443/openmeetings/screensharing/red5.jar
Which is normal as it try to get http on an https port. I tried to run it in my browser and get the confirmation:
400 Bad Request
Bad Request
Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.
Hint: https://www.euryecetelecom.com/
Maybe I am not configuring it properly, but I think that it might be a tiny bug. For you to check, the related part of config.xml:
443
https
I'll put my hands in the code to try to solve this and help a bit, but in case you know where it is...
was:
First, thanks Maxim for your answer and sorry to re-open it, I used a newer version - 2.1.0.r1428678-04-01-2013 and still have some issues (not the latest, I just tried to upgrade, but it failed to start and I got many error messages), so maybe it is already fixed. Just to explain the configuration better:
Public IPv4 Network - Forwarded Ports : 443/https to Machine 1 + 8088/rtmpT to Machine 2
Machine 1 : Apache Server https over 443 / proxy to Machine 2 clear http
Machine 2 : OpenMeetings Server - configuration: http over 5080 + rtmpT over 8088
Everything works fine here except the part where you click on share screen, you download
Related part of config.xml:
443
https
> OpenMeetings behind a proxy doesn't work for screen sharing
> -----------------------------------------------------------
>
> Key: OPENMEETINGS-431
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-431
> Project: Openmeetings
> Issue Type: Bug
> Components: Screen-sharing
> Affects Versions: 2.1 Apache Release
> Environment: CentOS 6.3 + OpenMeetings Nightly Build
> Reporter: Guillaume Rembert
> Assignee: Maxim Solodovnik
> Priority: Minor
> Labels: apache, forward, front-end
> Fix For: 2.1 Apache Release
>
>
> First, thanks Maxim for your answer and sorry to re-open it, I used a newer version - 2.1.0.r1428678-04-01-2013 and still have some issues (not the latest, I just tried to upgrade, but it failed to start and I got many error messages), so maybe it is already fixed. Just to explain the configuration better:
> Public IPv4 Network - Forwarded Ports : 443/https to Machine 1 + 8088/rtmpT to Machine 2
> Machine 1 : Apache Server https over 443 / proxy to Machine 2 clear http
> Machine 2 : OpenMeetings Server - configuration: http over 5080 + rtmpT over 8088
> Everything works fine here except the part where you click on share screen, you download public_9.njlp and execute it in javaws.
> I get the following error:
> com.sun.deploy.net.FailedDownloadException: Unable to load resource: http://meeting.myorganisation.com:443/openmeetings/screensharing/red5.jar
> Which is normal as it try to get http on an https port. I tried to run it in my browser and get the confirmation:
>
>
> 400 Bad Request
>
> Bad Request
> Your browser sent a request that this server could not understand.
> Reason: You're speaking plain HTTP to an SSL-enabled server port.
> Instead use the HTTPS scheme to access this URL, please.
>
Hint: https://www.euryecetelecom.com/
>
> Maybe I am not configuring it properly, but I think that it might be a tiny bug. For you to check, the related part of config.xml:
>
> 443
>
> https
> I'll put my hands in the code to try to solve this and help a bit, but in case you know where it is...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira