Closed fedot closed 7 years ago
@fedot
Thanks for reporting this. This inconsistency is happening because the multi-part upload returns the location URI encoded, whereas when the uploader does a putObject
(single part) upload, we generate the Location
ourselves.
We'll have to see what format the other SDKs return Location
as, but we should be able to at least make it consistent across all upload calls.
Hi! Just wanted to mention that we've noted the same issue.
We're working around it by rebuilding the url from the Bucket
and Key
parts of the response as those are consistent.
AWS.S3.ManagedUpload
callback may getLocation
property with url which has URI encodedpathname
(/
replaced by%2F
) if it's a multi-part upload.This is response for a 6mb file upload:
s3.upload(params).send(...)
This is response for uploading same file but with only one part:
s3.upload(params,{partSize: 10 * 1024 * 1024, queueSize:1}).send(...)