better content-type for wasm

[eminence]

Type: Enhancement

Description:

I'd like to use ipfs to host small applications written in web assembly. Currently the public ipfs gateways are serving webassembly files (.wasm extension) with the application/octet-stream content-type. However browsers require that web assembly files be served with the application/wasm content-type.

This enhancement request is for the IPFS gateways to use the correct content type for .wasm files.

CC ipfs/infra#433

[Stebalien]

Possibly related to #4025

[lidel]

Related:

• In this blog post Temporal announced support for custom ?ctype= parameter
  (I was unable to test because their gateway was down at the time of writing this)
• alternative proposal: manifest file for the IPFS gateway Proposal: manifest file for the IPFS gateway #6214

[eminence]

Turns out this was fixed a while ago in 2e87ac8 🎉

This is pretty cool because now entirely self-contained webassembly apps can be deployed to / run from IPFS

[mar1n3r0]

Hey @eminence I am trying this with go-app.

Would you mind sharing how did you manage to produce a self-contained wasm application and to load it in the browser?