Subscribe to:
Post Comments (Atom)
skip to main |
skip to sidebar
This blog has been moved to http://cosier.wordpress.com
Blog Archive
-
▼
2006
(95)
-
▼
December
(8)
- 0.cells is null or not an object – ASP.NET 2.0 Men...
- Switching/Changing WSS v3.0 site masterpage
- ASP.NET 2.0 Menu – MenuItemClick not posting back/...
- Element “ScriptManager” is not a known element. T...
- Using SSL host headers in IIS6.0
- Webcasts available in audio format
- Xml Notepad 2007
- WSS v3 application templates
-
▼
December
(8)
Links
About Me
- Matthew Cosier
- Matthew Cosier is a Principal Consultant at Hazaa, http://www.hazaa.com.au Matthew also manages an online blog about Software Development and all things Microsoft at http://cosier.wordpress.com
3 comments:
This will only work with wildcard domain SSL certificates. *.abc.com.
Example:
Host www.abc.com on identifier 1 with SSL cert assigned as www.abc.com on ip 1.1.1.150
Also host www2.abc.com on identifier 2 with SSL cert assigned as www2.abc.com on ip 1.1.1.150. (Both on standard SSL port 443)
This will not work because IIS uses only one cert per IP/Port. So when you try to goto www2 IIS will serv up www.aba.com's certificate to the client. And the cleint will warn about invalid cert for the site, because www2.abc.com does not match www.abc.com.
Now, if you have a wildcard domain certificate, like *.abc.com. Then it will work fine, as the wildcard will match both sites.
I have this set up and running for with a wildcard cert but now I add another IP address and a single SSL cert to the server and I can't seem to get the single domain cert to work with the new IP address. Have you seen this issue?
This will not truly have success, I consider so.
Post a Comment