|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Multiple SSL sites served from a single content pathHi there,
I wonder if anyone could help me with this? I have several versions of essentially the same web site, each has its own common name domain name, mysite1.com etc., and each is required to run in SSL mode. I intend to set these up as separate IIS web sites on the same server, each with its own IP address and each with its own certificate, which appears to be the only reasonable solution available to me. So my question is this, is it safe to point each of these IIS sites to the same local path so that they each run the same code (ASP.NET 2.0), or does this cause some sort of resource contention problem? Thanks very much, TH. that is fine
Show quoteHide quote "TH" <thinkt***@googlemail.com> wrote in message news:1164811184.844601.35310@14g2000cws.googlegroups.com... > Hi there, > > I wonder if anyone could help me with this? > > I have several versions of essentially the same web site, each has its > own common name domain name, mysite1.com etc., and each is required to > run in SSL mode. > > I intend to set these up as separate IIS web sites on the same server, > each with its own IP address and each with its own certificate, which > appears to be the only reasonable solution available to me. > > So my question is this, is it safe to point each of these IIS sites to > the same local path so that they each run the same code (ASP.NET 2.0), > or does this cause some sort of resource contention problem? > > Thanks very much, > TH. > IIS is perfectly fine with such a configuration.
If your websites are named: subdomain1.domain.com , subdomain2.domain.com , etc Then with IIS6 on Windows Server 2003 SP1 you can configure a single website with one IP address and one SSL wildcard Certificate for *.domain.com . //David http://w3-4u.blogspot.com http://blogs.msdn.com/David.Wang // TH wrote: Show quoteHide quote > Hi there, > > I wonder if anyone could help me with this? > > I have several versions of essentially the same web site, each has its > own common name domain name, mysite1.com etc., and each is required to > run in SSL mode. > > I intend to set these up as separate IIS web sites on the same server, > each with its own IP address and each with its own certificate, which > appears to be the only reasonable solution available to me. > > So my question is this, is it safe to point each of these IIS sites to > the same local path so that they each run the same code (ASP.NET 2.0), > or does this cause some sort of resource contention problem? > > Thanks very much, > TH. 
Other interesting topics
MS IIS Setting: HTTP Failed To Connect if Using Machine Name
Diff behavior for "Integrated windows authentication" in IIS6 Vs I How to create a web application on SBS2003 server ? RPC over HTTPS for Exchange "Failed to access IIS metabase" after installing Windows XP Pro Constrained Delegation Problem: SQL partially delegated Security Alert: The Name of the Security Certificate Is Invalid or Does Not Match the Name of the Si IWA connect to fileserver Non-default website is asking for username and password: why? Wrong cert for ssl site shows up |
|||||||||||||||||||||||
