CORS settings for self-hosted WASM blazor

[FLAMESpl]

Hi,

I am building a web app using WASM blazor, but for some reasons I need to allow external web page to make XHR requests for my index.html (building one SPA from multiple projects). For production deployments we are using nginx as a server and everything is OK there, but for local development I would like not to have this dependency.

So far I have successfully tried using ASP.NET hosted WASM blazor with kestrel launch and following configuration:

            services.AddCors(options =>
            {
                options.AddPolicy("CorsPolicy", builder => builder
                    .SetIsOriginAllowed(_ => true)
                    .AllowAnyMethod()
                    .AllowAnyHeader()
                    .AllowCredentials());
            });

ASP is responding to preflight requests and browser allows JS to load my index. It is already better, but ideally I would have it somehow configured for a self-hosted deployment when I use Visual Studio run button or CLI dotnet run .... I know there is a way to supply webconfig for IIS, but we are doing some development on Linux and I want solution self-contained as much as possible.

Is it possible with Kestrel?