Dear Hemant,

Would you be kind enough to share the Apache SSL configuration? Wearefacing issues in connecting through “proxy HTTPS + OM HTTP”. We are using a different proxy server, but can learn from your Apache configuration to adapt to our proxy.

I use it in a virtual subdirectory of the main server. This is also the reason for the reverse proxy need.

<Location /openmeetings/>
        ProxyPass http://localhost:5080/openmeetings/
        ProxyPassReverse http://localhost:5080/openmeetings/
RequestHeader edit Referer "https://www.example.com/openmeetings"; "http://localhost:5080/openmeetings";

        RewriteEngine on
        RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC]
        RewriteCond %{HTTP:CONNECTION} Upgrade$ [NC]
        RewriteRule .* ws://localhost:5080%{REQUEST_URI} [P]

#       LogLevel info rewrite:trace5

#       Require all denied
</Location>


How isyour configurationdifferent from this: _____http://mail-archives.apache.org/mod_mbox/openmeetings-user/201805.mbox/%3Ctrinity-46cc4ce2-542c-4f5a-872b-ae86bbb100c4-1526140744656@3c-app-mailcom-bs02%3E_<http://mail-archives.apache.org/mod_mbox/openmeetings-user/201805.mbox/%3Ctrinity-46cc4ce2-542c-4f5a-872b-ae86bbb100c4-1526140744656@3c-app-mailcom-bs02%3E>?

The only difference I see is the `RequestHeader` directive from the mod_headers. The problem was that the login was refused as OM/red5 detected some malicious setting due to unmatching domains.

I hope this can help you.

Christian
--
Mit freundlichen Grüßen
Christian Wolf

Waldwiese 9-11
66123 Saarbrücken
Mobil: 0178 776 79 39

Reply via email to