S3 DeleteObjects - Change in keys with XML characters

[debora-ito]

On January 10, 2024, we released a fix for a bug where calling S3 DeleteObjects with a key that contains characters that need to be escaped in XML and that is encoded, would incorrectly delete the object with the decoded key instead. This fix may break customers who currently rely on the previous behavior, and encode such keys when calling DeleteObjects.

DeleteObject works fine, this bug was only present in DeleteObjects.

Example:
decodedKey = "<Key>objectId</Key>"
encodedKey = "<Key>objectId</Key>"
doubleEncodedKey = "<Key>objectId</Key&gt"

Previous behavior:

Calling DeleteObjects with encodedKey would delete the object with the key decodedKey.
To properly delete the object with the key encodedKey, the workaround was to specify doubleEncodedKey as the key.

New behavior:

Calling DeleteObjects with encodedKey will delete the object with the key encodedKey.
Calling DeleteObjects with doubleEncodedKey will delete the object with the key doubleEncodedKey.

The fix was released as part of version 2.23.0