Deleting a S3 delete marker creates a new delete marker

[Fydon]

Describe the bug
I enabled preserving modification date and then uploaded a new file to a S3 bucket. I deleted it, which created a delete marker. I deleted the previous version, i.e. the file itself, which completed successfully. I then deleted the delete marker, but it just creates a new delete marker.

To Reproduce
Steps to reproduce the behavior:

1. Download S3 (Credentials from AWS Command Line Interface).cyberduckprofile
2. Edit it to add the following, as mentioned here.

    <key>Properties</key>
    <array>
      <string>s3.listing.metadata.enable=true</string>
    </array>

3. Change a S3 connection to use profile and connect
4. Upload a file to S3
5. Delete file
6. Delete previous version of file
7. Try to delete the delete marker

Expected behavior
Before enabling the preservation of the modification date, I was able to delete a delete marker. I'm still able to on another installation of Cyberduck using the same profile but without the above changes to enable preserving modification date.

Desktop (please complete the following information):

• OS: Windows 11
• Cyberduck Version: 9.0.4 (42232)

Log Files
Delete and list was over 2000 lines long, so just extracted delete.
cyberduck.log

Additional context

[dkocher]

As indicated by @Fydon this cannot be reproduced with the default AWS S3 connection profile but with the S3 (Timestamps) profile that has set s3.listing.metadata.enable=true. In this case file attributes are retrieved for every file using HEAD ¹ which is not supported for delete markers and causes us to dismiss the version ID.

Footnotes

1. https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadObject.html ↩