'Blazor Wasm always requesting all dlls when accessed outside of localhost

Using a simple app based on the Blazor Wasm demo app, if I run the application locally using

dotnet MyApp.dll

Calling localhost:8080 - the app loads with 48 requests

Calling using my PC host: dangerousbrian:8080 - the app loads with 262 requests, most of which are dll requests

Why is this? A lot of the 262 requests return a 304, but it's still a lot of uneccessary requests, and it seems to manage it ok on localhost.

The relevant part of Program.cs is probably this: There's nothing unusual in here though

var app = builder.Build();
app.Urls.Add("http://*:8080");
app.UseExceptionHandler("/Error");
app.UseHsts();
app.UseHttpsRedirection();
app.UseSession();
app.UseBlazorFrameworkFiles();
app.UseCors("CorsPolicy");
app.UseAuthentication();
app.UseResponseCompression();
app.UseRouting();
app.MapRazorPages();
app.MapControllers();
app.UseAuthorization();


Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source