7.2.2

• Fixes HTTP return code of DeleteObject operation (Thanks to @almirsarajcic!)

7.2.1

• Fixes error message when using erroneous access credentials (Thanks to @guitarrapc for reporting this!)

7.2

Attention! This release "unbreaks" an unintended breaking change introduced in release 7.0.2. Since that version, keys with special characters (excluding the forward slash /) were encoded twice, leading to wrong file names. After upgrading to this release, the respective objects will need to be re-uploaded, as the wrongly named objects cannot reliably be migrated.

• Fixes listing of objects with prefix (Thanks to @Chocobozzz for reporting this!)
• Fixes file name encoding error introduced in #171 (release 7.0.2)

7.1.2

Merge pull request #176 from scireum/jge/175

also publish a latest tag image name fixes #175

7.1.1

• Fixes Docker base image for Java 16

7.1

• Java 16

7.0.2

• Fixed bugs affecting keys with special characters (like /, spaces, or emojis)

7.0

Attention! This is a release with breaking changes. Create a backup of your data before upgrading! Migrated data is not compatible with earlier versions of S3 Ninja!

If you encounter any issues, including conditions such as wrong sorting order, please get in touch.

• Bucket name rules are now enforced strictly. In particular, bucket names need to have between 3 and 63 characters. They must consist of numbers, lower-case letters, dots and hyphens, and the first and last character need to be a letter or a digit. Upper-case letters, spaces and other characters are not legal.
  • Legacy buckets with illegal names are hidden. In order to show them again, rename the respective folders manually.
  • To do so within a Docker environment, obtain the container name via

    docker ps

    and obtain a shell:

    docker exec -it <container name> /bin/bash

• Object keys can now contain arbitrary UTF-8 characters, including slashes. In order to support this, data storage on disk was changed. The system attempts to migrate existing buckets automatically.
  • If your object keys used to contain forward slashes (/), automatic migration will yield a file name with underscores, due to an erroneous legacy coding scheme.
• URLs in the UI (accessible via /ui) have been adapted.
• Faulty output when querying ACLs of non-existing buckets has been fixed.
• Deletion of non-existing buckets leads to a 404 error now.

6.5.2

• Fixes bug in hash computation