Hi, I have the simple upload code using the aws js api
AWS.config.region = 'nyc3';
const spacesEndpoint = new AWS.Endpoint('nyc3.digitaloceanspaces.com');
const s3 = new AWS.S3({
endpoint: spacesEndpoint,
accessKeyId: '',
secretAccessKey: ''
});
var params = {
Bucket: bucket,
Key: key,
ContentType: file.type,
Body: file,
ACL: 'public-read'
};
var upload = s3.upload(params, function (err, data) {
if (err) {
console.log(err);
}
});
Everytime I upload a file large enough for a multipart upload, I get the error
ETagMissing: No access to ETag property on response. Check CORS configuration to expose ETag header
but in my CORS config, I’ve given all domains access to everything!
Do Spaces not support the ETag header required for this?
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi. You can upload CORS file configuration by s3cmd tool.
python s3cmd setcors cors.xml s3://[bucket]
Sample cors.xml:
<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<CORSRule>
<AllowedOrigin>*</AllowedOrigin>
<AllowedMethod>POST</AllowedMethod>
<AllowedMethod>PUT</AllowedMethod>
<AllowedMethod>DELETE</AllowedMethod>
<MaxAgeSeconds>3000</MaxAgeSeconds>
<ExposeHeader>ETag</ExposeHeader>
<AllowedHeader>*</AllowedHeader>
</CORSRule>
</CORSConfiguration>
It works for me:)
Click below to sign up and get $100 of credit to try our products over 60 days!
Getting the same results. I do see
ETag
headers listed in the documentation, so it is a bit confusing. https://developers.digitalocean.com/documentation/spaces/#common-headersDoes Digitalocean not have the ability to set “Expose Header” in CORS config, like on AWS? https://github.com/aws/aws-sdk-js/issues/191#issuecomment-28551382
Did you find a solution ? I’m also getting the same error message