You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2016/12/12 10:15:58 UTC
[jira] [Updated] (OPENMEETINGS-1507) Remove "application.base.url"
configuration key
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik updated OPENMEETINGS-1507:
-------------------------------------------
Fix Version/s: 4.0.0
3.2.0
3.1.4
> Remove "application.base.url" configuration key
> -----------------------------------------------
>
> Key: OPENMEETINGS-1507
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1507
> Project: Openmeetings
> Issue Type: Improvement
> Components: Screen-sharing
> Affects Versions: 3.1.3
> Environment: Centos 6.8
> Reporter: Maurizio Barbagin
> Assignee: Maxim Solodovnik
> Priority: Minor
> Fix For: 3.1.4, 3.2.0, 4.0.0
>
>
> When OpenMeetings server is connected to both a local network (http://server.local:5080/openmeetings) and Internet (http://server.domain.com:5080/openmeetings), java screen sharing application use always "application.base.url" configuration key as server address.
> So it's impossible to use screen sharing from both access types.
> I suggest using HTTP_REFERER dinamically for retrieving current application url, especially when it's used behind a reverse proxy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)