Thanks, that did the trick. I didn't notice that you can specify a port on
a NamedVirtualHosts directive. I realized that from your example. Once I
changed my entry to:
NameVirtualHost 192.168.0.101:80
then all of a sudden the HTTPS port was no longer part of a Named set of
virtual hosts, and it works.
This is great, because it means I only need one httpd running at a time, and
can serve both my named virtual hosts AND the SSL pages. Thanks again.
--Chris
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of David Marshall
Sent: Thursday, July 19, 2001 11:53 AM
To: '[EMAIL PROTECTED]'
Subject: RE: http and https, same instance
I do not use mod_ssl, but I'm using SSL and NamedVirtualHosts on Apache
1.3.19...
try this
NameVirtualHost 192.168.0.101
### Definition for some http (non SSL) virtual hosts
<Virtual 192.168.0.101:80>
ServerName "host1.blah.blah.blah.com"
# definition for this virtual host
</Virtual>
<Virtual 192.168.0.101:80>
ServerName "host2.blah.blah.blah.com"
# definition for this virtual host
</Virtual>
NameVirtualHost 192.168.0.101:443
### Definition for SSL - ALL port 443!
<Virtual 192.168.0.101:443>
<Location />
SSLRequireSSL
</Location>
</Virtual>
-----Original Message-----
From: Christopher Piggott HOME [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 19, 2001 8:49 AM
To: [EMAIL PROTECTED]
Subject: http and https, same instance
Is it reasonable to expect to run some http and some https traffic on the
same instance of apache 1.3 ?
I have named virtual hosts, and I understand they don't work with mod_ssl,
but what if I want something like this:
NameVirtualHost 192.168.0.101
### Definition for some http (non SSL) virtual hosts
<Virtual 192.168.0.101:80>
ServerName "host1.blah.blah.blah.com"
# definition for this virtual host
</Virtual>
<Virtual 192.168.0.101:80>
ServerName "host2.blah.blah.blah.com"
# definition for this virtual host
</Virtual>
### Definition for SSL - ALL port 443!
<Virtual _default_:443>
<Location />
SSLRequireSSL
</Location>
</Virtual>
####################
In other words, I don't care if the virtual named hosts work properly for
SSL, I just want it to work - and it's ok if HTTPS exists outside of any
virtual host.
I have thought of adding a second instance of the server, with its own
config file (or switches in httpd.conf using <IfDefine SSL>) ... but I don't
really want to lose the usefulness of apachectl. I don't know of a
convenient way to do this other than brute force.
Thanks,
--Chris
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
