I've looked at the "about:config" autofill settings, and that didn't
resolve it.
I also realize that Firefox is designed to use "https://google.com"; in
the latest version (21.0)
Chrome is installed on the Windows Server, and it defaults to
"https://yourhostname"; also.
I'm simply wondering if something in the Integrator or something in SOGo
is triggering HTTPS
I have not implemented HTTPS in the Apache configuration, so it should
not be seeking HTTPS although that may be a simple answer to the issue
(configure HTTPS for Apache on the SOGo ZEG)
On 06/22/2013 07:55 AM, stev...@cinergymetro.net wrote:
I recently updated Thunderbird to SOGo Integrator 17.0.6, and it works fine.
However, the web interface defaults to "https" when it's not configured to do
so.
There may be something else happening with Firefox 21 or Windows Server 2008R2
that's unknown.
Typing "http://sogo.domainname.com/SOGo/"; into Firefox finds the right page.
However, after inserting username/password, it defaults to
"https://yourhostname/SOGo/so/user/Calendar/";
Any hints? I'm thinking there's an extension that's causing Firefox to default
to HTTPS
Some pages but not all default to HTTPS (e.g., "google.com" but not
"mozilla.org") SOGo is not configured for HTTPS access, so unless the
Integrator changed something, it's not happening.
I'm just trying to eliminate issues. As I've said, it may have nothing to do
with SOGo
--
users@sogo.nu
https://inverse.ca/sogo/lists
