I and a part of my team use CloudBerry Explorer to uploaded images and videos on our S3 Amazon server that we use on our site. We're using the freeware version.

The way we use it is that we've connected the app to our server through the private key, etc. Next, whenever we have to upload a file, we just drag and drop it into the app or from a Windows folder in our S3 bucket.

This went OK until some months ago when I noticed that the images and videos are uploaded with the following HTTP Content-type head: binary/octet-stream. This may prevent Google from crawling and indexing the files.

Moreoever, the Cache-control value is wrong: "maxage" instead of "max-age".

From what I've found in the app with the help of a developer colleague (I'm not a developer), these two HTTP headers are "user defined":
Content-type
Cache-control

To note, I can manually update these HTTP headers by right-clicking the files in the app. However, I was hoping to fix this issue.

My colleague tried finding the issue on our side, no luck so far. Could this problem be related to CloudBerry?

I believe it has something to do with the way the files are read.

We've uploaded these extensions: GIF, PNG, JPG, MP4

The extensions are also defined in the Extensions' List in CloudBerry.