On Thu, 6 Mar 2003, Terry Kerr wrote:
> Hi,
>
> I am running apache 1.3.26 and mod_ssl 2.8.9-2.1 on a debian linux system.
>
> The system has two IP's, and I only wish for apache to start on ports 80 and 443
> on one of those IPs. I am using named based virtual hosting for many sites on
> the system for http, and have just one virtual host setup for https on port 443.
> The problem that I am having is that I cannot stop mod_ssl from binding to
> port 443 on both the IP's on my system. I have tried every possible combination
> of Listen, BindAddress, and Port, and have managed to prevent http from starting
> on all IP's, but https still starts on all IPs. Is there any way to stop this?
>
> Will I need to start two seperate servers, one serving http only, and one
> serving https only? If I was to do this, I may as well go back to using
> apache-ssl which is the default installation on debian anyway.
>
add the IP address or FQDN to the port designation for the appropriate
listen paramater:
<IfDefine SSL>
Listen someplace.com:80
Listen someplace.com:443
</IfDefine>
> Thanks in advance
>
> terry
>
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
admin & senior security consultant: sysinfo.com
http://sysinfo.com
"Cutting the space budget really restores my faith in humanity. It
eliminates dreams, goals, and ideals and lets us get straight to the
business of hate, debauchery, and self-annihilation."
-- Johnny Hart
testing, only testing, and damn good at it too!
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
