You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current implementation of library sets the mime type of a file for which it doesn't know the extension to text/plain. I recently had a situation where I had to upload .msi files to wordpress backend. If a mime type is not explicitly passed as a parameter to Media.Create method then it will set the mime type to text/plain. I think for the unrecognized extensions application/octet-stream is a more correct fit according to: https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Current implementation of library sets the mime type of a file for which it doesn't know the extension to text/plain. I recently had a situation where I had to upload .msi files to wordpress backend. If a mime type is not explicitly passed as a parameter to Media.Create method then it will set the mime type to text/plain. I think for the unrecognized extensions application/octet-stream is a more correct fit according to: https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types
Beta Was this translation helpful? Give feedback.
All reactions