-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Greetings!
With the help of the mailing list archives, I've gotten SSL
transactions functional on one name-based vhost, and other non-SSL vhosts
working as well. I understand that I can only have one port 443 server
name running on the machine.
However, is it possible to have apache generate an error message
of some sort when trying to https:// to one of the non-SSL vhosts? For
example consider the following configurations:
- - foo.com:80
- - foo.com:443
- - bar.com:80
- - bar.org:80
- - etc.
With an http://foo.com, all works as expected, an https://foo.com
works properly, as do http://bar.com and http://bar.org. However, when
entering https://bar.com or https://bar.org, I get a warning that the
server is offering a certificate for a differently-named server. If I opt
to accept it anyway under NS, I get the contents of https://foo.com,
though the location bar shows https://bar.com.
Is it possible to have an https request to the non-SSL vhosts get
killed without rolling over to the one SSL config?
Thanks for the great support lists, and excellent code!
- -Phil Hagen
- --
http://identityvector.com/~phil/ (PGP Key, software, etc)
PGP key also at http://www.keyserver.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjwyiqAACgkQ/5g75OFK7JNJuQCdHsGvuP3T4Wywsr8S8McFVDGS
vBwAn1YXl2XHsDYV5l45MWMDkAHRCb2s
=Qhmt
-----END PGP SIGNATURE-----
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
