NET Core 2.0 and custom base URL routing

I’ve been following an issue on StackOverflow which (in summary) shows that there is a problem hosting a .NET Core v2.0 service stack application at a specific URL.

I am having exactly the same problem as I have just upgraded to .NET Core 2.0; I quite like the solution proposed where the application specifies the HandlerFactoryPath as this seems like the native ServiceStack way to specify the base route for the application (and also appears to be respected by the metadata page in my own test).

Is there any way to get round the problem that occurs (documented in the same stack-overflow post which was only just recently updated) when using 'HandlerFactoryPath?

This is a breaking change they’ve added in .NET Core 2.0, we’ll investigate to see if there’s a workaround but otherwise I’d avoid fighting .NET Core conventions and just host it on a port and use a reverse proxy to implement the desired base hosting url.