-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Mime] fixed wrong mimetype #32986
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Mime] fixed wrong mimetype #32986
Conversation
The list there is automatically computed so we cannot patch it like that. |
So I better revert my changes and catch this error in the |
yes please |
Wouldn't it be better to change the code that generates the list to exclude non valid values? |
And where are these lists generated? Should this code be changed or should a check be added on the |
|
I removed the od* file extensions from the generator script. |
84816c4
to
e1722c5
Compare
Thank you @rjwebdev. |
This PR was squashed before being merged into the 4.3 branch (closes #32986). Discussion ---------- [Mime] fixed wrong mimetype | Q | A | ------------- | --- | Branch? | 4.3 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #32816 | License | MIT When creating a datapart from an odt file (and some other extensions), the explode function for the picked mimetype gives a wrong result since there's no `application/` prefix for the first mimetype of this extension. In this PR, all mimetypes without a prefix are removed. Commits ------- e1722c5 [Mime] fixed wrong mimetype
When creating a datapart from an odt file (and some other extensions), the explode function for the picked mimetype gives a wrong result since there's no
application/
prefix for the first mimetype of this extension.In this PR, all mimetypes without a prefix are removed.