Resolving issues with incorrect MIME-types of objects when uploading them to Object Storage
Issue description
- You encounter errors when accessing objects uploaded to Object Storage (images are not displayed, scripts do not work).
- The JavaScript console of the browser shows errors about an invalid mime-type of objects uploaded from the bucket.
Solution
Object Storage reports that the objects uploaded to the buckets have the Content-Type specified during the upload.
If the Content-Type was omitted at upload, objects are assigned the default object Content-Type: binary/octet-stream.
Check the configuration of the S3 client you previously used to upload objects to the bucket specifies a relevant Content-Type. You need to explicitly specify it when uploading a file to the bucket. You can also specify it for previously uploaded objects via the S3 client or SDK of your choice:
aws s3 cp --endpoint-url=https://storage.yandexcloud.net
s3://
s3://
--exclude ''
--include '.js'
--no-guess-mime-type
--content-type="application/javascript"
--metadata-directive="REPLACE"
--recursive
s3cmd put --recursive
--exclude ""
--include ".js"
--no-mime-magic
--add-header="Content-Type: application/javascript"
--no-preserve
--acl-public
/path/to/local/directory
s3://
If the issue persists
If the above actions did not help solve the problem, create a request for technical support.
When creating the request, provide the following information:
- Bucket ID in Object Storage.
- Link to the problematic object.
- Output from the JS console of the browser with the error or HAR file.