I am building a few web sites in asp.net core (multiple user interface applications and a web api app). They all work together, utilising the web api. For the purpose of my question we'll call them App1, App2 and App3. I am hosting my websites in IIS.
Typically, in the old .net Framework (4.5.1), I would have one website in IIS, with multiple web apps to host my multiple applications. Like so:
If the website (WebSite1) runs on port 443 (using the SSL cert), that means all apps are accessible via one domain url as follows:
https://www.myapp.com/App1/
https://www.myapp.com/App2/
https://www.myapp.com/App3/
With different app names at the end of the url to identify them.
When hosting the new asp.NET Core applications, I host in IIS as well, and following the documentation for asp.NET Core web site deployment, I host each .NET Core web app in a different site within IIS.
As I have one domain name for all my sites, for example, https://www.example.com (I'm using an SSL cert), I have to give the other websites different ports. So I end up with something like this:
WebSite1 - running on port 443
WebSite2 - running on port 444
WebSite3 - running on port 445
All of these apps are then accessible via these domain name urls:
https://www.example.com/ or https://www.example.com:443/
https://www.example.com:444/
https://www.example.com:445/
How do I host asp.NET Core applications all under one website as different "Applications", meaning they resolve to the same domain name url (https://www.example.com and the forward slash app name identifies which app we want)? OR alternatively, how do I take what I have configured now with the ports and route them all so App1 is default for example.com/, App 2 is example.com/app2/, and App 3 is example.com/app3/?
Am I looking at this .NET Core deployment completely the wrong way?
Thanks in advance for any pointers!
You could use a reverse proxy for serving multiple ASP Net Core application on the same domain.
Using IIS I'm not quite sure but you need to install URL Rewrite and then follow the documentation provided by Microsoft (also this one should be helpful).
You can also use nginx using location and proxy_pass as follow:
...
Some nginx Configuration
location /App1 {
proxy_pass http://127.0.0.1:443;
}
location /App2 {
proxy_pass http://127.0.0.1:444;
}
location /App3 {
proxy_pass http://127.0.0.1:445;
}
Other configurations...
And then, each time you want add another ASP Net application to your domain you'll need to add another location, run the application on a different point and restart nginx.
You don't need to create a site for each app, you can host it as before, as web applications inside one site. The only thing you need to do is select unmanaged app pool for your .Net Core applications, that's it. So this works:
https://domain/app1 and https://domain/app2 and you only need 1 certificate for a web server
Alternatively, you can create site for each app, then you need a sub-domain for each app, like https://app1.domain and like https://app2.domain
In this case all sub-domains must point to the same IP (if your server only have one) and you need to set up bindings for each site\app to it's domain. You should bind all sites to the same port (443 or 80).
For SSL in multiple sites configuration if you have IIS 7 you need to have a wildcard certificate. In IIS 8 and above you can use Server name indication feature and have a separate certificate for each site, however I recommend you to use wildcard certificate as well since SNI is new and might not be supported by some browsers
In both cases you need to set up a Windows Server Hosting from here Microsoft's download center
For IIS, you can use Application Request Routing (ARR) which combine with URL rewrite module to routing request into each the association between URL port.
It is used to build a similar proxy like Nginx and point to an appropriate port following each pattern of the URL.
You can see a sample with ARR below:
https://www.iis.net/learn/extensions/url-rewrite-module/reverse-proxy-with-url-rewrite-v2-and-application-request-routing
Try it: In file Web.config each application has a different name: <add name="herenewappname" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
I got this working using the advice for Sub-applications here: https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-2.2#sub-applications.
Here's the meaty part, in case the link dies:
To host an ASP.NET Core app as a sub-app under another ASP.NET Core
app:
1.Establish an app pool for the sub-app. Set the .NET CLR Version to No Managed Code because the Core Common Language Runtime (CoreCLR) for
.NET Core is booted to host the app in the worker process, not the
desktop CLR (.NET CLR).
2.Add the root site in IIS Manager with the sub-app in a folder under the root site.
3.Right-click the sub-app folder in IIS Manager and select Convert to Application.
4.In the Add Application dialog, use the Select button for the Application Pool to assign the app pool that you created for the
sub-app. Select OK.
As a bonus, my main application is legacy Web Forms and my sub-application is exciting new .NET Core functionality.
Happy days.
