I'm seeing something strange.

I've followed this to enable Lazy Loading of modules in my App.

7ded0a0

Once the App loads and I navigate to the route via URL it works without issue. URL is /configuration just to note.

However, once I'm on that /configuration module, if I do a hard refresh, it's like the MVC backend kicks in and attempts to resolve the Controller/Action (which obviously doesn't exist)

My MVC routes haven't changed and are base:

            app.UseMvc(routes =>
            {
                routes.MapRoute(
                    name: "default",
                    template: "{controller=Home}/{action=Index}/{id?}");

                routes.MapSpaFallbackRoute(
                    name: "spa-fallback",
                    defaults: new { controller = "Home", action="proxy.php?url=https%3A%2F%2Fgithub.com%2Faspnet%2FJavaScriptServices%2Fissues%2FIndex" });
            });

Am I missing something here? Why would "MVC" be trying to load /configuration instead of letting it fall to Angular?

NOTE: If I change the route to "config" reloading/navigating works as expected. Is something special about "configuration" (seems very odd to me unless I'm overlooking something)