Re: Apache Front end for Tomcat

2019-04-22 Thread Aaron Hepp
Question for the ones that moved to letting Apache2 be the web front end.  Do you experience long delay times when logging in and high CPU useage then when you was going into Tomcat directly? On 4/21/19 12:14 AM, Maxim Solodovnik wrote: I guess you need something like this: https://httpd.apach

Re: Apache Front end for Tomcat

2019-04-22 Thread Maxim Solodovnik
Hello Aaron, our demo servers using Apache as front-end proxy, I see no delays On Tue, 23 Apr 2019 at 02:22, Aaron Hepp wrote: > > Question for the ones that moved to letting Apache2 be the web front end. Do > you experience long delay times when logging in and high CPU useage then when > you

Re: Apache Front end for Tomcat

2019-04-22 Thread Stefan Kühl
Morning! Same to me. Using apache with multiple vHosts on a vps and the redirection works with the port number (ssl at 5443). So, if you call https:\\www.domain.com:5443 it will redirect you automatically to openmeetings. Wors well with OM 5.0. The quality is great and no delays ;-) Greetz S

Re: Apache Front end for Tomcat

2019-04-22 Thread Maxim Solodovnik
We using Apache to serve HTTPS So it works as Apache+SSL <--> OM+HTTP :) On Tue, 23 Apr 2019 at 11:26, Stefan Kühl wrote: > > Morning! > > Same to me. Using apache with multiple vHosts on a vps and the redirection > works with the port number (ssl at 5443). So, if you call > https:\\www.domain.

Re: Apache Front end for Tomcat

2019-04-22 Thread df8oe
That are exactly the conditions I want to setup my new OM instance. Thank you for your report - I will give it a try. Regards Andreas Am Dienstag, 23. April 2019, 06:25:53 CEST schrieb Stefan Kühl: > Morning! > > Same to me. Using apache with multiple vHosts on a vps and the > redirection works