* fix(s3api): reject an invalid storage class before uploading the body
* fix(s3api): reject an invalid storage class on CreateMultipartUpload
* fix(s3api): validate storage class and tags before reading the PUT body
* fix(s3api): validate storage class and tags with the other PUT headers
Checking them next to ValidateRequestEncryption keeps the check ahead of
any later hook that may answer the PUT without reaching putToFiler.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(s3api): reuse validatePutHeaders in putToFiler
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(s3api): store storage class and tags on directory-marker PUTs
The marker path validated x-amz-storage-class and x-amz-tagging but its
mkdir callback never wrote them, so a valid value was accepted and then
dropped and GetObjectTagging on the marker came back empty. Store both
the way putToFiler does.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(s3api): read directory-marker tags back through GetObjectTagging
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Chris Lu <chrislusf@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
