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

Don't check the mimetype via content.file.mimetype #51

Merged
merged 1 commit into from
Aug 10, 2021

Conversation

anoadragon453
Copy link
Member

Fixes #50.

This field is not actually specced. The specced field is at content.info.mimetype, which isn't currently sent to the content scanner.

We check the mimetype of the file by scanning the file itself. As issue #49 mentions, this check is not infallible, but that should be fixed separately.

This field is not actually specced. The specced field is at content.info.mimetype,
which isn't currently sent to the content scanner.

We check the mimetype of the file by scanning it. As issue #49 mentions, this
check is not infallible, but that should be fixed separately.
Copy link
Member

@jaywink jaywink left a comment

Choose a reason for hiding this comment

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

Looks good, thanks, and thanks for the context links 👍

@anoadragon453 anoadragon453 merged commit 1bd098d into main Aug 10, 2021
@anoadragon453 anoadragon453 deleted the anoa/remove_basic_mimetype_check branch August 10, 2021 17:27
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.

Consider as optional the mimetype in the file description
2 participants