While trying to address NXP-27091, we found that Blobs uploaded using FileManager.Import get their mime type normalised by default and due to "noMimeTypeCheck" parameter.
On the other hand, when the Blobs are uploaded using REST API, the mime type is not normalised.
If, in theory, MimetypeIconUpdater would be the one responsible for the normalisation, it only occurs for very specific situations (please see here).
It would be interesting to understand which should be the default behaviour, how can we get some coherency on blob uploads and also, how can we handle compatibility because documents with "non normalised" mime types would existing and customers and add-ons may rely on those mime types.
- depends on
-
NXP-20641 Allow mime-type check to be disabled on FileManager.Import
- Resolved
- is related to
-
NXP-27091 Fix application/x-photoshop blob preview
- Resolved
-
NXP-26779 Inconsistent mimetype in webui file drag and drop
- Resolved
-
NXP-23231 Error in MimetypeIconUpdater listener, segment question cannot be resolved
- Resolved
- is required by
-
ELEMENTS-882 Refactor document preview
- Open
- Is referenced in