Provide HTTP(s) Integration with Apache: Difference between revisions
(New page: =Providing both http and secure https access to users via webmail= ===Scenario=== Single production server, with public IP address running apache web server hosting multiple virtual dom...) |
|||
| Line 1: | Line 1: | ||
= | =Setting up HTTP and HTTPS support through Apache VirtualHosts= | ||
===Scenario=== | ===Scenario=== | ||
Single production server, with public IP address running apache web server hosting multiple virtual domains, and Zimbra Groupware server to | 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=== | ===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'. | |||
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=== | |||
*[http://httpd.apache.org/ Installed Apache webserver] | |||
*[http://httpd.apache.org/docs/1.3/vhosts/examples.html Familiarity with Apache VirtualHost configurations] | |||
=Laying the foundations= | |||
===Plan of Action=== | |||
*Install | |||
Revision as of 01:59, 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.
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).
System Requirements
Laying the foundations
Plan of Action
- Install
