Extending a Web Application to Use SSL
We presently have on web application used to host several host-header site collections. The initial web application was defined using a port value then extended using a host header over port 80. This works fine and we are able to access sites, albeit only
after adding each site collections' FQDN to the IIS site's host header collection, which seems to be a grossly underdocumented step. So Basically, the environment is as follows:
http://spwfe01:10168 (Default)
http://intranet.domain.com:80 (Intranet)
What I'm attempting to do is extend this again to another IIS site primarily for SSL access to the web application and all of it's site collections. Unfortunately, if I do just this, I can't access any of the sites via SSL. Do I once again have to bind all
of the site collections to port 443 using adsutil to get it to work or am I missing something?
May 20th, 2010 4:13pm
Thanks for the links. My question is more in regards to my use of host-header site collections.
Free Windows Admin Tool Kit Click here and download it now
May 20th, 2010 5:40pm