- Files are downloaded with unexpected file extension
- Files are downloaded without a file extension
SAP Business ByDesign
SAP Cloud for Customer
When attachments are uploaded, their mime type is determined based on the extension of the file name (e.g. example_file.pdf results in mime type “application/pdf”).
You map mime types and extensions and specify which mime types may be uploaded in the activity “Allowed MIME Types for Document Upload” in Business Configuration.
If the mime type cannot be determined from the file extension because the file extension is not maintained, mime type “application/octet-stream” is automatically used instead. Due to this behavior, we recommend not allowing mime type “application/octet-stream” without a purpose to prevent, for instance, the upload of executable or other unwanted file types.
In integration scenarios (SOAP, OData) the sender may specify the mime type. In this case, the mime type is used as specified and not determined based on the extension.
When downloading an attachment, the extension of the file name is used. If no extension is available or the extension doesn’t match the mime type, the maintained default extension of the mime type will be used.
In the Business Configuration activity “Allowed MIME Types for Document Upload”:
- Do not assign the same extension to a forbidden and an allowed mime type at the same time. For example, You add 2 new MimeTypes (eg: ZABC and ZDEF) but should not have same extension assigned. This should be avoided
- We recommend not to allow mime type “application/octet-stream”.
In integration scenarios
- Ensure that the file name contains an appropriate extension (e.g. the <Name> tag in SOAP messages).
- If the mime type is specified in integration scenarios, ensure the mime type / file extension matches the setting in “Allowed MIME Types for Document Upload” to avoid unwanted changes of the extension during download.
Mime types, attachments, file extension , KBA , AP-RC-DOC , Document Centric Application Service , Problem