Hi Nikolaj,
Whole point of having SSL is to "cover" the external users including the
mobile ones. What kind of problems I could face? If I can not manage to
have both (SSL and non-SSL), in that case I would prefer to have only
SSL access.
Thanks, Igor
P.S. My previous mail had some formatting issues.
Николай Клименко wrote, On 30/10/2012 20:01:
hi
it's not a good idea cause if you have mobile users you can face with
the problem that they can be outside .
30.10.12 20:02, Igor Vitorac пишет:
I would like to setup both SSL and non-SSL access to SOGo:
- SSL for accessing SOGo from outside of the company
- non-SSL for internal access.
In the SOGo.conf (httpd), there is a section for SOGo proxy:
<Proxy http://127.0.0.1:20000/SOGo>
RequestHeader set "x-webobjects-server-port" "80"
RequestHeader set "x-webobjects-server-name" "sogo.mydomain.com"
RequestHeader set "x-webobjects-server-url" "http://sogo.mydomain.com";
......
......
How can I introduce mentioned 3 properties for SSL in the same config?
Do I need to create dual SOGo configs: one virtual host for port 80
and one virtual host for port 443?
Thanks,
Igor
--
--
users@sogo.nu
https://inverse.ca/sogo/lists
