Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
jameslittle230 opened this issue Feb 22, 2022 · 2 comments
Open

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

jameslittle230 opened this issue Feb 22, 2022 · 2 comments
Labels
distribution An issue with the distribution/release of Stork, either for the current release or the broader proce

Comments

@jameslittle230
Copy link
Owner

Full error:

stork.wasm is returned with the wrong content type on stork-search so we fallback to WebAssembly.instantiate
@ArsenArsen
Copy link
Contributor

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

@jameslittle230
Copy link
Owner Author

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.

@jameslittle230 jameslittle230 self-assigned this Mar 15, 2022
@jameslittle230 jameslittle230 added distribution An issue with the distribution/release of Stork, either for the current release or the broader proce and removed type:bug labels Mar 17, 2023
@jameslittle230 jameslittle230 changed the title Investigate Webassembly.Instantiate browser error WASM isn't being served from Cloudfront with application/wasm content type Mar 17, 2023
@jameslittle230 jameslittle230 removed their assignment Mar 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
distribution An issue with the distribution/release of Stork, either for the current release or the broader proce
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jameslittle230 @ArsenArsen