[mezza]

Ok. Did a fresh reinstall of Zimbra (again). Set webmail ports to 8080 and 8443 (SSL) and set mode to 'mixed'.

Zimbra web interface responds on ports 8080 and 8443 as expected and

curl -i http://FQDN:8080

gets me a 302 redirect as expected to https://FQDN:8443.

The Apache Proxy and ProxyPass directives in my original post work fine, and all I'm contending with is how to get the 302 redirects between the secure and insecure ports working properly with a RewriteRule or Redirect directive (more on that later).

Very very concerningly,

sudo /opt/zimbra/bin/tomcat restart

is still complaining about not being able to reach the LDAP server, and after doing so, Zimbra's webmail interface no longer responds on port 8443, instead of which I get the login page on port 8080. The same thing happens if I use /opt/zimbra/bin/zmcontrol to restart Zimbra.

The only way I am able to get the webmail working again is to rerun the zmsetup.pl script.

Any ideas on what's going on?

Back to the RewriteRule, can anyone tell me why this doesn't work:

<VirtualHost XXX.XXX.XXX.XXX:80>
        ServerName FQDN
        ServerAdmin XXX@FQDN2
        DocumentRoot "/Library/WebServer/Documents"
        DirectoryIndex index.html index.php
        CustomLog "/var/log/httpd/access_log" "%h %l %u %t \"%r\" %>s %b"
        ErrorLog "/var/log/httpd/error_log"
        ErrorDocument 404 /error.html
        Redirect abacus https://FQDN/
        ProxyPass /abacus !
        ProxyPass / http://FQDN:8080/
        ProxyPassReverse / http://FQDN:8080/
        ProxyPassReverse /abacus/ https://FQDN:8443/
        LogLevel warn
</VirtualHost>

All I'm doing is to try and get the initial 302 redirect to https://FQDN:8443 to be rewritten to http://FQDN/abacus/... and then to catch that with a redirect rule to pass it to https://FQDN. Currently, as I have the insecure and secure ports set to 8080 and 8443, all the redirects are between those two ports when trying to login.