---
title: "ASP.NET Core server"
slug: "aspnet-core-server"
description: "Integrate your knowledge base into your website with a subfolder setup, ensuring seamless access and avoiding duplicate content issues for better SEO."
updated: 2026-06-26T06:33:12Z
published: 2026-06-26T06:33:12Z
canonical: "docs.document360.com/aspnet-core-server"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.document360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ASP.NET Core server

Hosting your Document360 knowledge base in a subfolder on ASP.NET Core, such as `example.document360.io/help`, lets you serve your documentation directly within your existing domain using a reverse proxy.

Replace the example domain in the configuration below with your own Document360-provided domain or custom domain.

---

## Before you begin

- Subfolder hosting works only when both the **Subfolder path** (for example, `/docs`) and the **Site API path** (for example, `/api`) are defined in Document360, with matching proxy configuration on your server.
- Install the <a href="https://www.nuget.org/packages/Microsoft.AspNetCore.Proxy/" target="_blank">ASP.NET Core proxy package</a>.

---

## How to configure a subfolder path in ASP.NET Core

In your `Startup.cs` file, configure the `Configure` method to route both UI and API requests, including proxy mappings for the **Subfolder path** (for example, `/docs`) and the **Site API path** (for example, `/api` or `/docs-api`):

```csharp
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
    // Proxy for /docs (Subfolder path)
    app.MapWhen(ctx => ctx.Request.Path.StartsWithSegments("/docs"),
        builder => builder.RunProxy(new ProxyOptions()
        {
            Scheme = "https",
            Host = "example.document360.io"
        }));

    // Proxy for /api (Site API path)
    app.MapWhen(ctx => ctx.Request.Path.StartsWithSegments("/api"),
        builder => builder.RunProxy(new ProxyOptions()
        {
            Scheme = "https",
            Host = "example.document360.io"
        }));
}
```

:::(Info) (<p class="fa-regular fa-circle-exclamation" data-type="icon"></p> NOTE)
Replace `/docs` and `/api` with the exact values configured under **Subfolder path** and **Site API path** in the Document360 portal.
:::

---

## What happens next

Once your server is configured, your knowledge base site is live on your custom subfolder. The existing Document360 URL continues to serve requests as well — for example, both `example.document360.io` and `example.com/docs` will point to your knowledge base site. This causes duplicate content in search engines like Google and Bing.

:::(Info) (<p class="fa-regular fa-circle-exclamation" data-type="icon"></p> NOTE)
To enable a redirect from your Document360 subdomain to your custom subfolder, contact <a href="https://document360.com/support/">Document360 support</a>.
:::

---

## Best practices

- Keep the Subfolder path and Site API path identical between the Document360 portal and your ASP.NET Core configuration to avoid broken routing.
- Test the proxy configuration in a non-production environment before applying it to your live domain.