better content-type for wasm on public gateways

ipfs / infra

Tools and systems for the IPFS community

MIT License

133 stars 41 forks source link

better content-type for wasm on public gateways #433

Closed eminence closed 5 years ago

eminence commented 6 years ago

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.

Would it be possible to reconfigure the ipfs gateways to use the correct content type for .wasm files?

ghost commented 6 years ago

You'll have to take this up with go-ipfs :)

mburns commented 5 years ago

discussion has moved to https://github.com/ipfs/go-ipfs/issues/5520