I'm trying to do some experiments using the threads support in webassembly projects.
With a basic project and minimal configuration it seems to be impossible to start in debug the project because the WasmAppHost tools returns incorrect headers while navigating the app.
Looking at the source code I noted that this middleware does not correctly handle files with extension .mjs .
Reproduction Steps
create a new browser wasm project dotnet new wasmbrowser
add <WasmEnableThreads>true</WasmEnableThreads> in the generated .csproj file under PropertyGroup
add a <PackageReference Include="Microsoft.NET.WebAssembly.Threading" Version="9.0.0-rc.1.24431.7" /> under ItemGroup
execute dotnet run or F5 in VS
Expected behavior
The http response for https://127.0.0.1:51986/_framework/dotnet.native.worker.14oy9i9plz.mjs must contains at least the following CORS header:
Cross-Origin-Embedder-Policy:require-corp
Edge report the error as in following screen:
A correct response is like this one for https://127.0.0.1:51986/_framework/dotnet.runtime.xw3lbfxs0o.js
Actual behavior
Currently no CORS headers are available in the response for https://127.0.0.1:51986/_framework/dotnet.native.worker.14oy9i9plz.mjs and so application bootstrap is interrupted by the browser.
Description
I'm trying to do some experiments using the threads support in webassembly projects. With a basic project and minimal configuration it seems to be impossible to start in debug the project because the WasmAppHost tools returns incorrect headers while navigating the app. Looking at the source code I noted that this middleware does not correctly handle files with extension
.mjs
.Reproduction Steps
dotnet new wasmbrowser
<WasmEnableThreads>true</WasmEnableThreads>
in the generated .csproj file underPropertyGroup
<PackageReference Include="Microsoft.NET.WebAssembly.Threading" Version="9.0.0-rc.1.24431.7" />
underItemGroup
dotnet run
orF5
in VSExpected behavior
The http response for
https://127.0.0.1:51986/_framework/dotnet.native.worker.14oy9i9plz.mjs
must contains at least the following CORS header:Cross-Origin-Embedder-Policy:require-corp
Edge report the error as in following screen:
A correct response is like this one for
https://127.0.0.1:51986/_framework/dotnet.runtime.xw3lbfxs0o.js
Actual behavior
Currently no CORS headers are available in the response for
https://127.0.0.1:51986/_framework/dotnet.native.worker.14oy9i9plz.mjs
and so application bootstrap is interrupted by the browser.Regression?
Not tested in previous versions
Known Workarounds
No
Configuration
Other information
No response