<div>
Well. sketch out what you have.. then you'll see, what the problem is: When a browser is using http instead of https, when you omit the protocol, then the request of the browser will be blocked by your FW. Thus using URL rewrite behind it is meaning less.<br />
<br />
The only thing you can do: Open port 80. Either on the FW and let the FW do the redirection (some appliances can do this) or just forward port 80 traffic from the FW to your IIS, so that you URL rewrite rules can be used.
</div>


Well. sketch out what you have.. then you'll see, what the problem is: When a browser is using http instead of https, when you omit the protocol, then the request of the browser will be blocked by your FW. Thus using URL rewrite behind it is meaning less.

The only thing you can do: Open port 80. Either on the FW and let the FW do the redirection (some appliances can do this) or just forward port 80 traffic from the FW to your IIS, so that you URL rewrite rules can be used.

<div>
Thank you @ste5an. So there's no way around that? let's say there where no rewrite rules, can it be handled by DNS or some other method so users type <a rel="ugc nofollow" target="_blank">subdomain.domain.com</a> and never have to worry about http or https ?
</div>


Thank you @ste5an. So there's no way around that? let's say there where no rewrite rules, can it be handled by DNS or some other method so users type subdomain.domain.com and never have to worry about http or https ?

Ralph Gould

<div>
<div class="content wysiwyg-content fr-view">
We have an IIS server and network solutions for DNS. IIS is running in house through a firewall. We DO NOT have port 80 for the website allowed. Only 443. We also have subdomains. I would like to enter <a rel="ugc nofollow" target="_blank">subdomain.domain.com</a> without any need to enter https and have it work, it does not currently. I must type in https:// for it to work. We have the url rewrite on but we are not using port 80 and I have the bindings in IIS only for 443 SSL. Any thoughts on how to resolve this would be greatly appreciated.&nbsp;
</div>
</div>



We have an IIS server and network solutions for DNS. IIS is running in house through a firewall. We DO NOT have port 80 for the website allowed. Only 443. We also have subdomains. I would like to enter
subdomain.domain.com
without any need to enter https and have it work, it does not currently. I must type in https:// for it to work. We have the url rewrite on but we are not using port 80 and I have the bindings in IIS only for 443 SSL. Any thoughts on how to resolve this would be greatly appreciated. 

Use HTTPS only

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.

Microsoft IIS Web Server

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.