Skip to content
This repository has been archived by the owner on Mar 25, 2022. It is now read-only.

better content-type for wasm on public gateways #433

Closed
eminence opened this issue Sep 17, 2018 · 2 comments
Closed

better content-type for wasm on public gateways #433

eminence opened this issue Sep 17, 2018 · 2 comments
Labels
status/deferred Conscious decision to pause or backlog

Comments

@eminence
Copy link

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
Copy link

ghost commented Sep 22, 2018

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

@ghost ghost closed this as completed Sep 22, 2018
@ghost ghost reopened this Sep 22, 2018
@eminence eminence mentioned this issue Sep 25, 2018
Closed
@eefahy eefahy added the status/deferred Conscious decision to pause or backlog label Jan 19, 2019
@mburns
Copy link
Contributor

mburns commented Nov 5, 2019

discussion has moved to ipfs/kubo#5520

@mburns mburns closed this as completed Nov 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
status/deferred Conscious decision to pause or backlog
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mburns @eminence @eefahy