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/11/16 06:01:58 UTC
[jira] [Commented] (OPENMEETINGS-1507) Remove
"application.base.url" configuration key
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669546#comment-15669546 ]
Maxim Solodovnik commented on OPENMEETINGS-1507:
------------------------------------------------
Hello Maurizio,
"application.base.url" can not be just removed due to it being used in different places, some of them are not connected to HttpRequest (like calendar email reminders)
HTTP_REFERRER can be used for screen sharing, but AFAIK it is not safe to use it while under reverse proxy.
for example see this answer: http://stackoverflow.com/questions/2648984/httpservletrequest-how-to-obtain-the-referring-url
Could you please describe why it is so vital to use server.local instead of server.domain.com simultaneously?
> 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
>
> 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)