-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Invalid character issue "" in AmazonS3Client::listMultipartUploads #3112
Comments
@navinyashende use ListMultipartUploadsRequest request = ListMultipartUploadsRequest.builder()
.bucket(BUCKET)
.prefix(PREFIX)
.encodingType(EncodingType.URL)
.build(); |
@debora-ito We are using abortMultipartUploads method in TransferManager which internally calls listMultipartUploads in the AmazonS3. |
I see. In this case, have you tried to manually url-encode the request attributes (like bucket and object name) before uploading? How the multipart upload is being done in the first place, is via |
@debora-ito The uploads are done from UI application via https://aws.amazon.com/sdk-for-javascript/. I was thinking if it would be possible to add encodingType in TransferManager class while making ListMultipartUploads request. This would make SDK immune to such issues. |
It would be nice but Java SDK v1 work is not being prioritized right now, ahead of the upcoming Maintenance Mode. The workaround here is to manually encode the upload request attributes. |
Upcoming End-of-Support
Describe the bug
Getting error while running listMultipartUpload method
Caused by: org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 599; Character reference "" is an invalid XML character.
Expected Behavior
Current Behavior
Caused by: org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 599; Character reference "" is an invalid XML character.
Reproduction Steps
Initialize s3 client and call listMultipartUploads
Possible Solution
Remove invalid character from XML response.
Additional Information/Context
No response
AWS Java SDK version used
1.12.725
JDK version used
openjdk version "1.8.0_402" OpenJDK Runtime Environment (build 1.8.0_402-b05) OpenJDK 64-Bit Server VM (build 25.402-b05, mixed mode)
Operating System and version
Fedora 40
The text was updated successfully, but these errors were encountered: