> I'm not sure I understand what you are saying. The web server can't tell
> the difference between a user typing https://somesite into their browser
> versus selecting a link to https://somesite from a web page.
When you created the link on the page, it would be
https://secure.hostingprovider.com/ rather then https://somesite
> Apache has no problem with name-based virtual hosting and SSL. We do it
all
> the time.
Not with vhosts based on host headers you don't.
> Microsoft's IIS by design doesn't support name based virtual hosts on
ports
> other than 80. They even have a KB article on the subject. I found this
> out a few weeks ago when helping a friend trying to get SSL running on
there
> second virtual host.
I have virtual hosts on several ports besides 80. It's simply an artifact
of the SSL protocol (SSL is negotiated BEFORE he host header comes through),
so as a result, you need some way for the server to tell which SSL cert is
appropriate. That method is based on the IP.
========================================================
Dave Warren,
Email: [EMAIL PROTECTED]
Pager: [EMAIL PROTECTED]
========================================================
