Can't set HTTP headers as arg to s3.put to ensure correct Content-Type is set #49649
Labels
Bug
broken, incorrect, or confusing behavior
fixed-pls-verify
fix is linked, bug author to confirm fix
P2
Priority 2
severity-medium
3rd level, incorrect or bad functionality, confusing and lacks a work around
Milestone
Description of Issue/Question
Setup
Using module.run s3.put to place HTML files in an S3 bucket.
Steps to Reproduce Issue
Try using s3.put to place an object into an S3 bucket.
As s3.put has no header argument available the correct Content-Type will not be set, e.g. text/html
The default is binary/octet-stream and this is what is currently set for any objects created using s3.put
Refer to: https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPUT.html
Versions Report
n/a - see pull request diff
The text was updated successfully, but these errors were encountered: