WASM isn't being served from Cloudfront with `application/wasm` content type

Open jameslittle230 opened this issue 4 years ago • 2 comments

Full error:

stork.wasm is returned with the wrong content type on stork-search so we fallback to WebAssembly.instantiate

Feb 22 '22 15:02 jameslittle230

I believe the CDN would need to return a application/wasm content type instead of an octet-stream to fix this.

Mar 14 '22 23:03 ArsenArsen

Yup, definitely. I think the missing context here is that I'm specifying an application/wasm content type in my script that uploads files to the CDN, but that content type isn't being plumbed through the infrastructure correctly.

If I had to guess, it's something goofy with my Cloudfront setup, but I have to do some more investigation to check.

Mar 15 '22 17:03 jameslittle230