Dan Delaney wrote:
> Hi all. What is the most common setup for having a normal server and
> a secure server on the same machine? Should I just have one instance
> of Apache running with a virtual domain that handles the https://
> connections? or should I actually start a separate httpd process
> that handles the https:// connections?
The simplest set-up is to compile in mod_ssl to produce an SSL-enabled
httpd binary (i.e. static-linking). Then you just start it with the
option "-DSSL" (all this is taken care of by apachectl). The server will
handle plain HTTP requests (port 80) as fast as an HTTP-only server
(I've never noticed any performance degradation). You use your existing
httpd.conf file with no modifications to non-SSL virtualhosts.
For SSL, you just define an SSL virtualhost, add in the necessary
Directives, and away it goes.
The only "disadvantage" is that the binary grows in size quite a bit
(from ~600K non-SSL to ~2M with mod_ssl). That shouldn't be a problem
unless your server is seriously under-resourced or you like to worry
about these things :-)
Rgds,
Owen Boyle
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
