fix #5229 - move IServerStartup.Configure execution until later so that it is possible to register custom endpoints
This commit is contained in:
@ -23,10 +23,6 @@ namespace Oqtane.Infrastructure
|
||||
var config = context.RequestServices.GetService(typeof(IConfigManager)) as IConfigManager;
|
||||
string path = context.Request.Path.ToString();
|
||||
|
||||
// note that in order to support Alias subfolders we used to ignore Blazor framework requests...
|
||||
// but this does not work in static rendering as the web UI request originates from /_blazor
|
||||
//if (config.IsInstalled() && !path.StartsWith("/_"))
|
||||
|
||||
if (config.IsInstalled())
|
||||
{
|
||||
// get alias (note that this also sets SiteState.Alias)
|
||||
|
@ -195,9 +195,6 @@ namespace Oqtane
|
||||
app.UseHsts();
|
||||
}
|
||||
|
||||
// execute any IServerStartup logic
|
||||
app.ConfigureOqtaneAssemblies(env);
|
||||
|
||||
// allow oqtane localization middleware
|
||||
app.UseOqtaneLocalization();
|
||||
|
||||
@ -248,6 +245,9 @@ namespace Oqtane
|
||||
.AddAdditionalAssemblies(typeof(SiteRouter).Assembly);
|
||||
});
|
||||
|
||||
// execute any IServerStartup logic
|
||||
app.ConfigureOqtaneAssemblies(env);
|
||||
|
||||
// simulate the fallback routing approach of traditional Blazor - allowing the custom SiteRouter to handle all routing concerns
|
||||
app.UseEndpoints(endpoints =>
|
||||
{
|
||||
|
Reference in New Issue
Block a user