Hello David,

The simplest solution here would be perhaps using Upload Rules that will set the correct headers for the files in question. Please keep us posted regarding the results.

Hello David,

The simplest solution here would be perhaps using Upload Rules that will set the correct headers for the files in question. Please keep us posted regarding the results.

Uh. I don't suppose you have an upload rule? I guess I would use the CLI and the rule would be of the form

If suffix = .html then content type = html ??

I'm going to get a license anyway

Hi. I asked about this issue over in Stackoverflow, and the comment from an independent certified amazon developer was that the problem is likely to to do with Cloudberry as Amazon won't change the type.

https://stackoverflow.com/questions/55979474/why-do-excel-published-static-html-files-have-content-type-octet-on-amazon-s3

That is correct, so you basically set it to the content type you are interested in and it should assign it properly. Now regarding changing it to octet i presume it is happening due to the way driver handles the files. We take a closer look at this issue with our R&D.

So I tried setting an upload rule from the "Managed Drive Options" . The rule sets uploaded files with suffix . html to be type text/html. However it doesn't change anything. I guess writing to a file on S3 from within Excel isn't seen as an upload.

Did you find a solution to this? Having the same problem. The upload rules seems to work when creating a new file. But if it's editing an existing file it seems to override text/html with application/octet-stream

You should be able to create a rule for this within the product. The issue with rules was addressed with the 180 version sometime ago. Can you verify what version you're running and if there was a reboot after the upgrade to 1.8? Also check your rules because if there are multiple rules for that file type, then only the first rule is applied on upload.

Thanks David. Yes that seems to have done the trick. My first rule where I was trying to apply it to only html files didn't seem to work. But the 2nd rule applying to all files when I was testing wasn't being applied.

We are having the same/similar issue. We just recently upgraded to 3.2.0.2 and seemed to break our rule.

See my comment above. Make sure you don't have duplicate rules.

Hi all - I thought it was worthwhile to repost this thread as there is a similar bug as before that I'm hoping can be noted?

It seems if you are running cloudberry drive without an internet connection (such as on a flight), it seems to default back to "application/octet-stream" when you next make a change or regain an internet connection.

Deleting all the files, deleting the upload rule, re-adding the upload rule, then resaving with an internet connection seems to fix it

I'm trying to remember to close cloudberry manually when I don't have internet but it's an easy thing to forget