Closed tim-finnigan closed 1 year ago
P90665777
This is a blocker for us. Our http-request client does by default add a contentType header which leads to SignatureDoesNotMatch errors.
We are using aws-sdk to generate presigned urls for multi-part uploads the following way:
s3.("uploadPart", {
Bucket: bucket,
Key: key,
Expires: expiresInS,
UploadId: uploadId,
PartNumber: partNo,
// "ContentType": contentType, // not allowed by aws-sdk
})
Allowing to specify a contentType for presigned url generation would solve it, is there any reason against it?
"aws-sdk": "2.1406.0",
We heard back from the S3 team and they created a backlog item for this feature request. We can't provide any ETAs or guarantees as to if or when this would be implemented. We recommend reaching out through AWS Support for updates in the future if you have a support plan, otherwise feel free to check back in here as well.
This issue is now closed.
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Hey what's the deal with this, it's breaking browser uploads to S3 Please escalate it.
Original issue: https://github.com/boto/boto3/issues/3708