Question: best practice Linux + nginx + subfolder in url

[Weboholics]

Hi,
We are having problem using subfolder in url, example:
http://domainName.com/weboholics
We have tried two approaches:

(What we think is the right way) Rewrite url in nginx
(nginx configuration)
rewrite ^(/weboholics)(.*)$ $2 break;
With this approach razor get confused and @Url.Action("Index","Home") returns:
/Home/Index when the correct url should be
/weboholics/Home/Index

We have asked others, and they have suggested to use WebHostBuilder().UseUrls("http://domainName.com/weboholics"), but seems not feasible due to our usage of Unix Socket
(our UseUrl)
.UseUrls("http://unix:/var/disk2/sparfiler/www/weboholics.sock")

Second approach - change routing

With this approach Razor Url.Action() works but this doesn't work in Razor:
(code)
<script type="application/ecmascript" src="~/ckeditor/ckeditor.js"></script>
Razor will render this to:
<script type="application/ecmascript" src="/ckeditor/ckeditor.js" ></script>
(How it should be)
<script type="application/ecmascript" src="/weboholics/ckeditor/ckeditor.js" ></script>

Our startup (both approaches )

public static void Main(string[] args)
        {
            var host = new WebHostBuilder()
                .UseKestrel()
                .UseContentRoot(Directory.GetCurrentDirectory())
                .UseUrls("http://unix:/var/disk2/sparfiler/www/weboholics.sock")
                .UseIISIntegration()
                .UseStartup<Startup>()
                .Build();

            host.Run();
        }

What is the correct approach for using subfolders? especially in an Linux + nginx environment?

Best Regards
Jesse / Weboholics

[Tratcher]

UseUrls("http://domainName.com/weboholics") is exactly how we handle this for IIS.
@halter73, is there a way to make this work for unix sockets? Maybe we should come up with one.

[davidfowl]

Can't there just be a middleware in the pipeline that sets the path base on http context? (that's effectively) what happens when you put the path in there anyways.

[Tratcher]

There could be, but this is a deployment parameter so it should be easily configurable. That's why we included it in the Server.

[davidfowl]

@Weboholics As a workaround add this code to your application's Startup.cs

public class Startup
{
   public void Configure(IApplicationBuilder app)
   {
      app.Map("/weboholics", ConfigureCore);
   }

   private void ConfigureCore(IApplicationBuilder app)
   {
        // Configure your pipeline here
   }
}

This should unblock you for now.

[halter73]

UseUrls("http://domainName.com/weboholics") is exactly how we handle this for IIS.

@Tratcher You sure about this? It looks to me that both UseUrls and UseIISIntegration clobber the WebHostDefaults.ServerUrlsKey with no regard for what was there previously. My underastanding is that if UseUrls is called after IISIntegration, then the proxying is completely broken. If IISIntegration is called second, UseUrls is ignored.

I see that aspnet/IISIntegration#14 is closed with a comment saying this has been fixed by the ASP.NET Core Module. I would like to know how. I don't see anything in IISIntegration that updates the PathBase which I think would be required.

[Tratcher]

It's here:
https://github.com/aspnet/IISIntegration/blob/dev/src/Microsoft.AspNetCore.Server.IISIntegration/WebHostBuilderIISExtensions.cs#L38-L39

It gets the base path from IIS/ANCM via environment variable and gives it to Kestrel to manage. (Note UseSetting and UseUrl do the same thing here).

Can we come up with a syntax for the user to specify a base path in UseUrls for the unix sockets scenario?

[davidfowl]

Feels like a hack. We should be using different fields for different data even in the default case.

[Weboholics]

@davidfowl Thanks. Your workaround seems to work. Looking forward for a final solution.

[muratg]

@DamianEdwards @shirhatti

Do we want this as a feature?

[DamianEdwards]

Yes pls

[muratg]

@shirhatti Can you come up with the requirements for 1.1.0?