Can you provide a link to an uploaded game that experiences this problem so I can take a closer look.
We’ll likely have to rely on a standardized file extension to be able to automatically apply these headers when extracting games.
Viewing post in Cross Origin Policies for Webassembly
for the standardized file I would suggest something like an empty .coopcoep file, or alternatively a yaml file for defining headers. Netilify has the following:
https://docs.netlify.com/routing/headers/#syntax-for-the-headers-file
A note, at current time, it appears that Netilify also doesn't support such specific headers - so investigate them before implementing.
Giving people directly control over headers is a security risk so I would prefer to have a something a bit more strict. Additionally, we have a lot of newer (and tired!) game devs uploading HTML5 games. I don’t want to push them into writing configuration files because it’s going to result in broken games, confusion & support tickets. Ideally something that transparently works.
On closer inspection I see that the document hosting the game must include those headers, and not the WASM code itself. I think that it’s probably safe to just apply those headers to all index.html files extracted for HTML5 games.