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 ASP.NET Core proxy package.

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):

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"
        }));
}

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.

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.