Metadata Content type problem with S3 Extension 2.0.*

I recently updated from 0.9.4 to the latest 2.0 RC. My use of the extension is exclusively for uploading XML files (sitemap.xml etc) to a bucket which serves them via proxy. I have a mapping in my application for the s3 bucket and I use fileMove() after building the xml files to upload them to S3.

I noticed that with version 0.9.4 of the extension, the MetaData “Content-Type” value for the s3 object was correctly set to “application/xml” but with the newer version ( and higher) it is set to “application/octet-stream”. This is a nuisance because it means Chrome will no longer display the sitemap.xml files in the browser, but instead prompts to save/download them.

Is this a bug? Or is there a way to specify the Content-Type value somehow? I assume not using fileMove() but I can explore other ways to move the files to s3 if I need to find a workaround.

I filed a bug [LDEV-3988] - Lucee

1 Like

Thanks Zac!

this should be fixed in the latest version