Skip to content
This repository has been archived by the owner on Sep 28, 2021. It is now read-only.

fix: fix content-type by doing a fall-back using extensions #5

Merged
merged 1 commit into from
Aug 2, 2018

Conversation

satazor
Copy link
Contributor

@satazor satazor commented Aug 2, 2018

The service-worker-gateway was only responding with the correct content-type for some mime-types, see https://github.com/sindresorhus/file-type#supported-file-types.
This commit now fall-backs to detecting based on the extension as well.

Note that SVGs aren't supported by the file-type module.

@satazor satazor force-pushed the fix-content-type branch 4 times, most recently from feea5e1 to d8688c0 Compare August 2, 2018 02:12
The JS IPFS gateway was only responding with the correct content-type for some mime-types, see https://github.com/sindresorhus/file-type#supported-file-types.
This commit now fall-backs to detecting based on the extension as well.

Note that SVGs aren't supported by the `file-type` module.
Copy link
Member

@vasco-santos vasco-santos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants