Difference between revisions of "Provide HTTP(s) Integration with Apache"

m
m
Line 10: Line 10:
 
===Aims===
 
===Aims===
  
*You want to provide both http (insecure) and https (secure) access to clients through the webmail interface.
+
* You want to provide both http (insecure) and https (secure) access to clients through the webmail interface.
  
On 'server.com' you want to provide webmail access when users visit 'http://webmail.server.com' and secure acces when they visit 'https://webmail.server.com'.
+
* On 'server.com' you want to provide webmail access when users visit 'http://webmail.server.com' and secure acces when they visit 'https://webmail.server.com'.
  
The Apache server listens on default ports 80 and 443, the Zimbra server listens on port 81 and uses the insecure login authentication method (zmtlsctl http).
+
* The Apache server listens on default ports 80 and 443, the Zimbra server listens on port 81 and uses the insecure login authentication method (zmtlsctl http).
  
 
===System Requirements===
 
===System Requirements===
  
*[http://httpd.apache.org/ Installed Apache webserver]
+
* [http://httpd.apache.org/ Installed Apache webserver]
*[http://httpd.apache.org/docs/1.3/vhosts/examples.html Familiarity with Apache VirtualHost configurations]
+
* [http://httpd.apache.org/docs/1.3/vhosts/examples.html Familiarity with Apache VirtualHost configurations]
 +
* [http://wiki.zimbra.com/index.php?title=Installation_Articles Working Zimbra installation]
  
 
=Laying the foundations=
 
=Laying the foundations=

Revision as of 02:04, 18 February 2008

Setting up HTTP and HTTPS support through Apache VirtualHosts

Scenario

Single production server, with public IP address running apache web server hosting multiple virtual domains, and Zimbra Groupware server to providing email and webmail access to users in multiple virtual domains.

The example domain used in this article is 'server.com' - replace with your own domain.

Aims

  • You want to provide both http (insecure) and https (secure) access to clients through the webmail interface.
  • The Apache server listens on default ports 80 and 443, the Zimbra server listens on port 81 and uses the insecure login authentication method (zmtlsctl http).

System Requirements

Laying the foundations

Plan of Action

  • Configure Zimbra to run on port 81.
  • Configure Zimbra to use simple http authentication.
  • Install a new virtual host to catch all webmail.server.com requests.
  • Install a new virtual host to catch all secure webmail.server.com requests.
Jump to: navigation, search