On Tue, Jun 17, 2003 at 09:29:33PM -0500, Will Trillich wrote: > On Tue, Jun 03, 2003 at 05:53:23AM -0700, [EMAIL PROTECTED] > wrote: > > On Tue, Jun 03, 2003 at 12:03:04AM -0400, ScruLoose wrote: > > > So I *think* what I need to do is to have two separate > > > invocations of apache running all the time: one listening > > > for http on port 80 and the other listening for https on > > > port, umm... 443 I think it was. > > > > Right. You will run two Apache servers. They have separate > > configs (separate /etc/apache* dirs) and separate logs. The > > don't conflict with each other. > > why would it be bad to have apache-perl with libapache-mod-ssl > active? that way if your login area does heavy mod_perl stuff > similar to the public mod_perl stuff, you won't have to maintain > two diverse branches. > > there's a drawback, i'm sure, but what is it?
Not sure I've got your question correct, but I think a common config would be a front-end server with ssl and proxy back the mod_perl requests to a mod_perl server. http://perl.apache.org/docs/1.0/guide/strategy.html#SSL_functionality_and_a_mod_perl_Server -- Bill Moseley [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
