STANDARD storage class omitted

[nikeee]

I'm building an S3 client and recently added S3Mock to the test matrix.

I noticed that the storage class is omitted when it's STANDARD. Looking at the changelog, this seems to be intentional:

S3Mock/CHANGELOG.md

Line 613 in db1e4a4

* Fix StorageClass, it's not returned for most APIs if it's "STANDARD"

The AWS docs declare StorageClass as nullable, so it's valid to omit it.

However, S3Mock is the only implementation - that I've tested so far - that does that. In my tests, AWS S3, Hetzner, Ceph, Garage, Minio, LocalStack and Backblaze include the storage class.

This brings up the question: As S3Mock is a mocking library that is used to reflect real-world-use, is this intentional?
I want to emphasize that it's technically valid to omit the storage class as per AWS docs. I'm just not sure whether that's what this project wants to do.

[afranken]

I tested all ITs against S3 in May 2024, and almost every test that validated the storage class if it was STANDARD failed against AWS APIs:
a97f2f3

Maybe that changed in the last 18 months?

[nikeee]

Maybe it only affects ListObjectsV2. It seems to be omitted by some services on ListMultipartUploads. Or it has changed. I'll check.

[afranken]

have you had time to check this yet?