Hello.
We have self-hosting omnibus instance 14.6.5-ee (open source) with local storage and we plan to migrate to an S3 provider with proxy_download
enabled.
After reading carefully the migration plan we decided to tests with uploads first.
Every thing looks good, our 587
uploads where copied to the object storage, unfortunately, avatar images and others are not rendered in the browser.
As an example, our logo PNG file has a content-type = application/octet-stream
instead of image/png
.
When I download the PNG logo file from our S3 provider locally, file
says it’s data
:
$ file /tmp/logo.png
/tmp/logo.png: data
$ file --mime /tmp/logo.png
/tmp/logo.png: application/octet-stream; charset=binary
When I open the file, there is some strange data before and after the PNG content:
$ head -n 2 /tmp/logo.png
1411;chunk-signature=97340e6c135a71c693ef017b009df3bdc2825e320c6fe2cc9ecb2f58becb06dc
�PNG
$ tail -n 2 /tmp/logo.png
0;chunk-signature=848797d5896fb59876bf61c19c31f330591ba9c6f4cb8dc3575ebca5ecfabdc2
Does someone have any clue about what is happening?