New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CopyObject fails for file starting with "/" #1241
Comments
Thanks for reporting this |
We have noticed this issue has not recieved attention in a year. We will close this issue for now. If you think this is in error, please feel free to comment and reopen the issue. |
I think this should be fixed or closed by someone other than the bot ;) |
This problem is bigger than just a failure to copy objects starting with "/". There's 3 possible "wrong" things that can happen: Incorrect Behaviour 1 Command: Copy "/abc" to "/def" Incorrect Behaviour 2 Command: Copy "/abc" to "/def" Incorrect Behaviour 3 Command: Copy "/abc" to "/def" Final Notes So when the source key starts with a '/' character, then the wrong file will be copied. When the destination key starts with a '/' character, then the file is copied to the wrong location, possibly destroying existing data in the destination bucket. Since |
Closing as duplicate of the new issue #1720. |
Copying files starting with "/" using CopyObject fails with the following message:
Expected Behavior
The file should copy correctly.
Note: Uploading the file with
PutObjectAsync
and reading the file withGetObjectRequest
works as expected.Steps to Reproduce (for bugs)
Here is a simple unit test that fails
Context
We're exchanging files with a 3rd party using S3 and for some reason they have prefixed their files with "/". We're writing a Lambda function that will trigger and process each file that is uploaded to the S3 bucket, and a part of the processing is copying the file to another bucket.
Your Environment
Installing AWSSDK.Core 3.3.100.3.
Installing AWSSDK.S3 3.3.101.1.
Installing NuGet package AWSSDK.S3 3.3.101.1.
The text was updated successfully, but these errors were encountered: