If a file has a special character in it (in this case, the endash "–"), it cannot be copied using s3.copyObject. Yet the odd thing is, S3 allows this character when the object is created. I can even create the file via the JS SDK with no problems, but copying fails.
S3 requires the copy source to be URL-encoded, and unfortunately introducing this behavior to the SDK would be a breaking change. Please see #1302 & #712 for further discussion.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.