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

[Ron Phipps]

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

>
> Oh one other thing, if the idea of running a secure server is frivilous as
>you say. Why would interchange be configured to ask you if there is a
secure
>server running under a different name?
>
>Beriah
>
>
>_______________________________________________
>Interchange-users mailing list
>Interchange-users@www.minivend.com
>http://www.minivend.com/mailman/listinfo/interchange-users
>