[ic] http running as one daemon | https running as another

[Beriah Dutcher]

I dont really have any sites that explain this in any detail. If you want
setup a test server and setup the two daemons. Make the ssl only listen on
443 and the non only listen on 80. run top and make a html page that open
20-30 browsers upon a hit and watch the server u have setup now sore on top
and suck up all it can. Then do the same on the two daemons and then also on
another machine access the ssl daemon and watch how the load works with
that. (i really recomend doign this ONLY across a lan)

Beriah

-----Original Message-----
From: interchange-users-admin@minivend.com
[mailto:interchange-users-admin@minivend.com]On Behalf Of Ron Phipps
Sent: Thursday, October 05, 2000 5:16 PM
To: interchange-users@minivend.com
Subject: Re: [ic] http running as one daemon | https running as another


A reason for this directive besides for seperate daemons is for those that
only have one SSL certificate.  The Cert is based on the domain name, we
give our clients the choice to purchase their own cert or to use ours.  If
they use ours then the secure pages are routed through our domain which is
why the SecureServer directive is needed.

I'd be interested to see the performance differences when running seperate
daemons.  We run our catalogs off of a SSL server that also serves non-ssl
pages and have not seen a decrease in performance, but if there is one we'd
look into running seperate daemons.  The way I understood it was that the
daemon 'knows' how to process the request since the SSL request comes
through on a port other then 80 (443 by default).  If this is incorrect do
you have any sites that explain how it works?  Thanks for the information!

-Ron