In this deployment tutorial we're going to setup a new production ready Windows 2019 web server on Microsoft Azure with IIS (Internet Information Services), then deploy a full stack Vue.js + ASP.NET Core + SQL Server application to it that supports user registration and JWT authentication.
In this deployment tutorial we're going to setup a production ready Windows + IIS server from scratch on Microsoft Azure, then deploy a full stack React + ASP.NET Core + SQL Server application to it that supports user registration and JWT authentication.
In this deployment tutorial we're going to setup a production ready web server from scratch on Microsoft Azure running Windows Server and IIS, then deploy a full stack Angular + ASP.NET Core + SQL Server application to it that supports user registration and authentication.
After setting up automatic redirects from HTTP to HTTPS you may start seeing browser warnings about "insecure content" or "mixed content" and some content may be blocked and not displayed, this is because some of the external content references in your html are still using an insecure "http://" url.
Redirecting multiple domains to one and http to https is a pretty common requirement, and the are plenty of examples online showing how to do this using the IIS URL Rewrite Module.
Most of the examples I've seen work fine, but use separate rules for redirecting each domain and for redirecting http to https, resulting in something like this:
