|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
1200+ fellow developers rate and compare features of the top IDEs, like Visual Studio, Eclipse, RAD, Delphi and others, across 13 categories. Enjoy this FREE Download of the IDE User Satisfaction Study by Evans Data Corporation. Download Now!
|
|
#1
|
|||
|
|||
|
Hi,
I am very new to IIS so sorry if the question seems abit dumb I think i should explain the structure of my smalll busines network first. I have a Linux Snapgear router which is use for NAT. We have three servers. Windows 2003 standard for AD, Windows 2003 web edition for ASP webpages, and Linux redhat for php and email servers etc.. We have one SSL website running at the moment on our windows 2003 web edition machine. This website is dynamic in that if you put default.asp?accountid=3 at the end it will go to another design. What I need to do is set up a domain with SSL certificate for each accountid. We have two at the moment but maybe we will have more in the future. On to the questions: 1.I called up verisign and they told me I need a different local ip for each certificate. Is this true? 2. How would i go about setting the server/network up so it will accept multiple SSL site on one server. I thought I could use headers to determine different site but I read up with SSL i can't do this. 3. I need one of the site to go to default.asp?accountid=3 by default. Since all the site uses the same folder as their root directory how would i do this? Thanks |
|
#2
|
|||
|
|||
|
I don't know, hopefully an IIS/SSL person jumps in here.
__________________
====== Doug G ====== "Hide, hide witch! The good folk come to burn thee. Their keen enjoyment hid behind their gothic mask of duty." -Mark Clifton |
|
#3
|
|||
|
|||
|
Hi,
Regarding the statement from Verisign I can confirm that this is true You need 1 SSL certificate for each IP address which is generated with your domain information as well.The answer to your 2nd question now is pretty much the same reason as the explanation above. Sorry! ========== r0adrunner ========== |
|
#4
|
|||
|
|||
Just change SSL port:- IIS prop -> Site1 -> Advanced -> 192.168.1.1 80 URL 192.168.1.1 443 - IIS prop -> Site2 -> Advanced -> 192.168.1.1 80 URL 192.168.1.1 444 SSL port:444 (or ...) To access that site(s) use: URL and URL ... and tra-tra-tra ... ![]() |
![]() |
| Viewing: Dev Shed Forums > System Administration > IIS > Multiple SSL site-one server-one nic |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|