<div>
to add to DJ's response: &nbsp;SSL requires it's own IP Address and doesn't support host headers. &nbsp;You'll need to bind another IP Address to the server in TCP/IP Properties and assign that to the SSL site.
</div>


to add to DJ's response:  SSL requires it's own IP Address and doesn't support host headers.  You'll need to bind another IP Address to the server in TCP/IP Properties and assign that to the SSL site.

<div>
Thanks guys. Makes sense. I noticed in the bindings section, once you select https, the host-header field grays out.<br />
<br />
I will do it.
</div>


Thanks guys. Makes sense. I noticed in the bindings section, once you select https, the host-header field grays out.

I will do it.

<div>
<div class="content wysiwyg-content">
I've configured IIS on a new install of Windows Server 2008 R2 and have setup numerous web sites. I imported my first SSL certificate and configured for only 1 site to use.<br />
<br />
Now I notice that if I add https to the URL of any other non-SSL site on that server, I will get re-directed to the site that has the SSL certificate. The URL will be the name of the other site but the SSL site is what loads.<br />
<br />
How do I prevent the other non-SSL sites from redirecting to the SSL site when https prefaces the URL.<br />
<br />
I noticed in IIS 6 that it throws a 'connection refused' error in this same scenario.<br />
<br />
I'm moving these sites from an old IIS 6.0 server to IIS 7.0.<br />
<br />
I know the simple answer is not to add https to the URL of the non-SSL sites :-0... but my QC department has raised this issue so I'm trying to find a solution. &nbsp;<br />
<br />
Thanks.
</div>
</div>


I've configured IIS on a new install of Windows Server 2008 R2 and have setup numerous web sites. I imported my first SSL certificate and configured for only 1 site to use.

Now I notice that if I add https to the URL of any other non-SSL site on that server, I will get re-directed to the site that has the SSL certificate. The URL will be the name of the other site but the SSL site is what loads.

How do I prevent the other non-SSL sites from redirecting to the SSL site when https prefaces the URL.

I noticed in IIS 6 that it throws a 'connection refused' error in this same scenario.

I'm moving these sites from an old IIS 6.0 server to IIS 7.0.

I know the simple answer is not to add https to the URL of the non-SSL sites :-0... but my QC department has raised this issue so I'm trying to find a solution.  

Thanks.

Adding https to URL of non=SSL site redirects to the SSL site

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

HTTPS is a protocol for secure communication over a computer network which is widely used on the Internet. HTTPS consists of communication over Hypertext Transfer Protocol (HTTP) within a connection encrypted by Transport Layer Security (TLS) or its predecessor, Secure Sockets Layer (SSL). The main motivation for HTTPS is authentication of the visited website and to protect the privacy and integrity of the exchanged data. HTTPS is widely used for protecting page authenticity on all types of websites, securing accounts and keeping user communications, identity and web browsing private.

SSL / HTTPS

IIS is Internet Information Services, the web server included with Windows Server operating systems. All current versions are built on a modular architecture; modules can be added or removed individually so that those required for specific functionality are installed. The full installation of IIS includes HTTP, security, content, compression, caching, logging and diagnostics.