Repository navigation
s3: Specifying e_tags in DeleteObjects operation results in MalformedXML error #1311
Description
Describe the bug
If I uncomment set_etag below
let Ok(oi) = aws_sdk_s3::types::ObjectIdentifier::builder()
.key(key)
// .set_e_tag(object.e_tag)
.build()
else {
continue;
};Then using this ObjectIdentifier as part of Delete results in
code: "MalformedXML", message: "The XML you provided was not well-formed or did not validate against our published schema",
Regression Issue
- Select this option if this issue appears to be a regression.
Expected Behavior
It should work.
Current Behavior
Malformed XML error
Reproduction Steps
Just make any DeleteObjects with E-Tag being populated. I'm deleting 1000 objects at a time.
See https://github.com/Fuuzetsu/aws-delete-objects-etag-repro
Possible Solution
No response
Additional Information/Context
No response
Version
aws-sdk-s3 = "1.90.0"
Environment details (OS name and version, etc.)
Linux
Logs
even with trace level the request body is not visible so logs aren't very useful
Activity
landonxjames commentedon Jun 19, 2025
Does this happen with any E-Tag value? Wondering if somehow an unexpected XML token is showing up in the E-Tag and confusing the parser.
Reproducer for awslabs/aws-sdk-rust#1311
Fuuzetsu commentedon Jun 20, 2025
I made a reproducer here: https://github.com/Fuuzetsu/aws-delete-objects-etag-repro
You can see the output in README.md there. While there, I was wondering if I can delete an object with etag with the
DeleteObjectAPI viaIf-Matchlike described at https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html#API_DeleteObject_RequestSyntax but that doesn't work either. Not sure if that's a separate issue or not.I noticed that the ETag from the list operation came in with double quotes around it. Stripping it didn't help. Sending an ETag that was just
fooalso didn't help.You can see in the output that I can delete the object just fine if I don't pass the ETag.
Let me know if you need more info.
Fuuzetsu commentedon Jun 20, 2025
For the DeleteObject, we can see some of the request in the trace logs. Not sure if it's useful but I include that bit below. One can run the reproducer with RUST_LOG=trace and see everything.