Gateway content type detection : ODS documents served as ZIP (MIME)

[hsanjuan]

Version information: 0.5.0

Description:

It seems http.DetectContentType does not work well for these types.

We could switch to https://github.com/gabriel-vasile/mimetype ? (also see https://stackoverflow.com/a/52266327 for more options). Unsure if there is a reason have have sticked with the current detector.

Related #2164

Reported at https://discuss.ipfs.io/t/bugs-in-0-5-0-regarding-file-names-types/7845

[Stebalien]

Sounds like a great idea!

[xmaysonnave]

Definitely room for improvement.
I made some experiment with gz contents. Nginx is able to gz content and modern browsers are able to properly deflate appropriately served gz html.
I really would like to proxy the proper content type. The filename trick while serving data blocks seems a good way to investigate. /ipfs/cid?filename=whatever.gz
Right while doing this, browsers open a save as dialog box.
Thanks.

[hsanjuan]

At first sight it seems you are mixing Content-Encoding and Content-Type @xmaysonnave ? For browsers to deflate on the fly, I think Content-Type should still be html, and Content-Encoding gzip.

If you add a gzip file directly to ipfs... well, the content type will be gzip.