-
Notifications
You must be signed in to change notification settings - Fork 180
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
aws sync broken since 2.1.29 #257
Comments
I just reproduced this locally. Unfortunately, this seems to have broken object listing, as the client expects several field values in the response to be encoded ( |
Ran into exactly the same original URL-encoding issue and the new breakage described here. |
I have a fix ready, just working on the tests right now - unfortunately the V1 and V2 APIs (or rather the client implementation of ListObjects vs ListObjectsV2) do different things when it comes to responses with encoding. I'm wondering if we have to keep supporting the V1 APIs in the mock... |
I'm still using V1 currently. One reason is that some features were only available in V1 at least until recently, such as DynamoDB client-side encryption: aws/aws-sdk-java-v2#34 |
I did not mean the Java SDK V1, but the API: It is possible to request both ListObjects as well as ListObjectsV2 with the V1 SDK: |
aws-cli expects no empty elements in encoded responses and will fail the request if it encounters an empty element. At least aws-java-sdk V1 and V2 worked fine with the current implementation, though. Fixes #257
aws-cli expects no empty elements in encoded responses and will fail the request if it encounters an empty element. At least aws-java-sdk V1 and V2 worked fine with the current implementation, though. Fixes #257
aws-cli expects no empty elements in encoded responses and will fail the request if it encounters an empty element. At least aws-java-sdk V1 and V2 worked fine with the current implementation, though. Fixes adobe#257
aws sync seems to be broken since 2.1.29.
Calling the command in it's basic form e.g.
aws s3 sync . s3://bucket --endpoint-url http://localhost:9090
produces the error fatal error: 'Prefix'.The same command works fine till version 2.1.28.
The text was updated successfully, but these errors were encountered: