Details
-
Bug
-
Resolution: Fixed
-
Major
-
6.2
-
None
-
-
Maintenance 58
Description
When uploading non-binary asset, the mime type is always shown as text/plain making it difficult to know when it is actually stored incorrectly.
The incorrect stored mime type case happens when uploading via zip-upload.
To reproduce (visual issue):
- upload non image file such as js or csv via upload field
- Observe resolved mime type (should be correct)
- save the asset
- open again for editing
- Observe resolved mime type (note that this is just a visual error, actual type stored in jcr is correct!)
To reproduce (in repo):
- pack an image in a zip file
- zip-upload file with image into dam via Assets app action
- observe stored mimetype (eg vie JCR Tools/Dumper or via export of the asset)
Checklists
Acceptance criteria
Attachments
Issue Links
- is cloned by
-
MGNLDAM-965 Mime types of files uploaded via Zip-Upload action are not resolved correctly
-
- Closed
-
- relates to
-
MGNLUI-6390 allowedMimeTypePattern property doesn't work as expected
-
- Closed
-