Incorrect Mime Type returned

[andrewmclagan]

Describe the bug

When uploading a Microsoft Word doc such as .docx tusd returns an incorrect mime header of

content-type: application/octet-stream

should be

content-type: application/vnd.openxmlformats-officedocument.wordprocessingml.document

This actually occurs for many file types. It actually seems to modify the actual file. Once we download it again and check the mime locally on a linux box its reading it wrong...

To Reproduce
Can reproduced on https://uppy.io/examples/dashboard/

Expected behavior
correct mime header

[andrewmclagan]

content-type: application/pdf

Pdfs word as expected

[Acconut]

Good finding! We currently (incorrectly) don't allow dots in the values for the Content-Type header, causing tusd to fall back to the default type of application/octet-stream.

It actually seems to modify the actual file. Once we download it again and check the mime locally on a linux box its reading it wrong...

This should never happen. Can you confirm that the file content is different using checksums (e.g. md5 or sha1)?

[andrewmclagan]

I will reconfirm this is changing the checksum. Could be on our side.

[andrewmclagan]

Yes they match. So thats all fine.

@Acconut

[Acconut]

Great, thanks for checking! I am going to close this issue since the incorrect mime type was fixed in 852b6fa which will be included in the next release.

[andrewmclagan]

Thanks. Will use a custom image build until it’s realeased.