Скачать или смотреть Deploying Multiple Websites on IIS: Setting Up foo.bar and api.foo.bar

Learn how to deploy your ASP.NET Core UI and Go API on IIS with proper configurations for seamless access.
---
This video is based on the question https://stackoverflow.com/q/76416119/ asked by the user 'Scrzii' ( https://stackoverflow.com/u/16506588/ ) and on the answer https://stackoverflow.com/a/76452292/ provided by the user 'Scrzii' ( https://stackoverflow.com/u/16506588/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Domain + subdomain IIS deployment

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Deploying Multiple Websites on IIS: Setting Up foo.bar and api.foo.bar

If you're navigating the complexities of web deployment, you may find yourself in a situation where you need to host multiple sites on the same domain. Perhaps you’re building a web application with an ASP.NET Core user interface (UI) and a Go API, and you want to serve both through the same domain.

For instance, you have a domain named foo.bar for your ASP.NET UI and you want to set up api.foo.bar for your Go API. But you run into issues like receiving 404 errors when trying to access your API site. Fear not! In this guide, we’ll walk through the steps to successfully deploy both sites on IIS (Internet Information Services), ensuring they can coexist without any hiccups.

The Problem

You have two web applications:

An ASP.NET Core web UI.

A Go API.

You want to set them up as follows:

Access the ASP.NET Core UI at foo.bar.

Access the Go API at api.foo.bar.

However, you’re encountering challenges, such as:

The API site returning a 404 error.

You are able to successfully access the Go server on port 8080 from the server's browser but not through the designated subdomain.

The Solution

To successfully deploy both your ASP.NET Core UI and Go API using IIS, follow these organized steps:

Step 1: Setup IIS Sites

First, we need to create two separate sites within IIS, one for each application.

Create the ASP.NET Core Site:

Open IIS Manager.

Right-click on "Sites" and select "Add Website...".

Set the site name to foo.bar.

Leave the hostname field blank to bind it to the root domain.

Point the physical path to the folder where your ASP.NET application resides.

Click OK.

Create the Go API Site:

Repeat the process and create another site named api.foo.bar.

Set the hostname to api.foo.bar.

Point the physical path to the folder for your Go API application.

Click OK.

Step 2: Configure URL Rewrite for the Go API

Now that both sites are established, we need to set up a rewrite rule to forward requests from api.foo.bar to your Go API running on port 8080.

Navigate to the api.foo.bar site in IIS Manager.

In the middle pane, double-click on the "URL Rewrite" feature.

Click on "Add Rule(s)..." in the right-hand actions pane and select "Blank rule".

Set up the following rule configuration:

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Test the Configuration

Once you have configured the rewrite rule:

Restart IIS to ensure that all changes are applied.

Go to http://foo.bar to access your ASP.NET Core UI.

Go to http://api.foo.bar to access your Go API.

If everything is set up correctly, both applications should function without any issues. Your ASP.NET UI should load in one tab, while the API should respond to requests on another without returning 404 errors!

Conclusion

Deploying multiple websites under a single domain using IIS involves setting up individual sites for each application and configuring URL rewriting for proper routing. By following the outlined steps, you can effectively run your ASP.NET Core UI and Go API concurrently, all while keeping them organized and accessible.

Whether you're a seasoned developer or just starting, understanding how IIS operates can significantly enhance your deployment process. If you encounter further issues or have questions, don't hesitate to reach out for help.

Remember, successful deployment is just a configuration away!