[JCLOUDS-1447] S3 CopyObject requires x-amz-copy-source to be URL encoded

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.1.1
• Fix Version/s: 2.2.0, 2.1.2
• Component/s: jclouds-blobstore
• Labels: s3
• Assignee: Andrew Gaul
• Reporter: David Currie
• Created: 07/Sep/18 14:32
• Updated: 12/Sep/18 18:43
• Resolved: 12/Sep/18 15:05

Description

S3 CopyObject requires x-amz-copy-source to be URL encoded as per https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectCOPY.html. Current failure to do so results in a 400:

org.jclouds.aws.AWSResponseException: request PUT https://cloudbees-kubernetes-arch.s3.amazonaws.com/jclouds-test/…/test0/2/artifacts/otherdir/xxx%23%3F:%24%26%27%22%3C%3E%C4%8D%E0%A5%90 HTTP/1.1 failed with code 400, error: AWSError\{requestId='…', requestToken='…', code='InvalidArgument', message='Unsupported copy source parameter.', context='{ArgumentValue=/cloudbees-kubernetes-arch/jclouds-test/…/test0/1/artifacts/otherdir/xxx#?:$&'"<>čॐ, HostId=…, ArgumentName=x-amz-copy-source}'}
 at org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.handleError(ParseAWSErrorFromXmlContent.java:75)
 at …
 at org.jclouds.s3.blobstore.S3BlobStore.copyBlob(S3BlobStore.java:324)

 

Issue Links

• relates to: JCLOUDS-1401 S3 SignatureDoesNotMatch when listing keys using prefix with ampersand
• links to: PR 1238