[
https://issues.apache.org/jira/browse/OPENMEETINGS-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992523#comment-16992523
]
Henrik Ek edited comment on OPENMEETINGS-2149 at 12/10/19 1:14 PM:
-------------------------------------------------------------------
Hello,
I found the problem. The problem was that the response header that OM sends in
return to the browser specifies Content-Security-Policy - ws://servername.xyz
which should be wss://servername.xyz.
I am using an apache httpd server as https to http proxy with the configuration
below where I have now added a row so that I edit the response header regarding
Content-Security-Policy so I fix ws: to wss:.
{code:java}
<VirtualHost *:80>
ServerName conference.xyz.se
Redirect / https://conference.xyz.se
</VirtualHost>
<VirtualHost *:443>
ServerName conference.xyz.se
SSLEngine on
SSLCertificateFile fullchain.pem
SSLCertificateKeyFile privkey.pem
RewriteEngine On
RewriteCond %{HTTP:Connection} Upgrade [NC]
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteRule /(.*) ws://OMserver.xyz.se:5080/$1 [P,L]
RedirectMatch ^/$ https://conference.xyz.se/openmeetings
ProxyPreserveHost On
RequestHeader edit Referer https: http:
RequestHeader edit Origin https: http:
Header edit Content-Security-Policy ws: wss:
<Location /openmeetings>
Require all granted
ProxyPass http://OMserver.xyz.se:5080/openmeetings
ProxyPassReverse http://OMserver.xyz.se:5080/openmeetings
RewriteEngine On
RewriteRule ^/(.*) http://OMserver.xyz.se:5080/$1 [P]
</Location>
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
</VirtualHost>
{code}
was (Author: henrikek):
Hello,
I found the problem. The problem was that the response header that OM sends in
return to the browser specifies Content-Security-Policy - ws://servername.xyz
which should be wss://servername.xyz.
I am using an apache httpd server as https to http proxy with the configuration
below where I have now added a row so that I edit the response header regarding
Content-Security-Policy so I fix ws: to wss:.
{code:java}
<VirtualHost *:80>
ServerName conference.xyz.se
Redirect / https://conference.xyz.se
</VirtualHost>
<VirtualHost *:443>
ServerName conference.essolutions.se
SSLEngine on
SSLCertificateFile fullchain.pem
SSLCertificateKeyFile privkey.pem
RewriteEngine On
RewriteCond %{HTTP:Connection} Upgrade [NC]
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteRule /(.*) ws://OMserver.xyz.se:5080/$1 [P,L]
RedirectMatch ^/$ https://conference.xyz.se/openmeetings
ProxyPreserveHost On
RequestHeader edit Referer https: http:
RequestHeader edit Origin https: http:
Header edit Content-Security-Policy ws: wss:
<Location /openmeetings>
Require all granted
ProxyPass http://OMserver.xyz.se:5080/openmeetings
ProxyPassReverse http://OMserver.xyz.se:5080/openmeetings
RewriteEngine On
RewriteRule ^/(.*) http://OMserver.xyz.se:5080/$1 [P]
</Location>
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
</VirtualHost>
{code}
> Safari users in iOS or macOS can not login to openmeetings
> ----------------------------------------------------------
>
> Key: OPENMEETINGS-2149
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2149
> Project: Openmeetings
> Issue Type: Bug
> Components: Mobile client
> Affects Versions: 5.0.0-M3
> Reporter: Henrik Ek
> Assignee: Maxim Solodovnik
> Priority: Major
>
> iOS mobile devices only have Safari as a browser and cannot be logged in to
> openmeetings. We receive the following error messages in the console:
> {code:java}
> Refused to connect to
> wss://conference.essolutions.se/openmeetings/wicket/websocket?pageId=3&wicket-ajax-baseurl=.&wicket-app-name=OpenmeetingsApplication
> because it does not appear in the connect-src directive of the Content
> Security Policy.
> {code}
> Possibly the following may be relevant information:
>
> [https://stackoverflow.com/questions/41102298/ios-refused-to-connect-because-it-appears-in-neither-the-connect-src-directive-n]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
