Peter B
2016-02-26 08:27:00 UTC
Hi,
Ubuntu 14.04, nightlies (currently 3.0.1.20160219).
Am loving SOGo, as a long time admin/user of several other platforms
(OX/Horde amongst them) I love the simplicity of SOGo from both admin
and user perspectives and that in the main it just works.
An observation - when getting DAV urls the provided URL doesn't reflect
correctly the protocol used to access the server. I've configured apache
to redirect all access via HTTPS, so anyone using SOGo is forced to use
an SSL connection. However, URLs displayed under "Links to ..." are
returned as HTTP.
This can present a problem, for example using this URL in Thunderbird
with the SOGo connector results in no synchronization, but no errors are
reported. This is because the server is returning a redirect and not the
data*. Change the URL from 'http://' to 'https://' and it works.
Ideally, SOGo web UI would present DAV URLs that reflect the protocol
used to access the Web UI.
Peter.
* Actually, thinking about it, is that a bug in the connector? Should it
follow the redirect or perhaps report an error? I've noticed that
Lightning doesn't have this problem when given an HTTP URL for the same
server, so I guess it's following the redirect. Either way, it would
still be good to show the relevant protocol in the URL provided...
Ubuntu 14.04, nightlies (currently 3.0.1.20160219).
Am loving SOGo, as a long time admin/user of several other platforms
(OX/Horde amongst them) I love the simplicity of SOGo from both admin
and user perspectives and that in the main it just works.
An observation - when getting DAV urls the provided URL doesn't reflect
correctly the protocol used to access the server. I've configured apache
to redirect all access via HTTPS, so anyone using SOGo is forced to use
an SSL connection. However, URLs displayed under "Links to ..." are
returned as HTTP.
This can present a problem, for example using this URL in Thunderbird
with the SOGo connector results in no synchronization, but no errors are
reported. This is because the server is returning a redirect and not the
data*. Change the URL from 'http://' to 'https://' and it works.
Ideally, SOGo web UI would present DAV URLs that reflect the protocol
used to access the Web UI.
Peter.
* Actually, thinking about it, is that a bug in the connector? Should it
follow the redirect or perhaps report an error? I've noticed that
Lightning doesn't have this problem when given an HTTP URL for the same
server, so I guess it's following the redirect. Either way, it would
still be good to show the relevant protocol in the URL provided...
--
***@sogo.nu
https://inverse.ca/sogo/lists
***@sogo.nu
https://inverse.ca/sogo/lists