fix(storage): disable acl list objects for new buckets#70
Conversation
Greptile SummaryThis PR disables directory listing by default on new buckets by unconditionally setting the
Confidence Score: 3/5
Important Files Changed
Last reviewed commit: ecfabb9 |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
ecfabb9 to
df957db
Compare
df957db to
fd890db
Compare
|
🎉 This PR is included in version 2.15.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.3.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.1.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.2.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Note
Medium Risk
Changes default bucket creation behavior by sending
ACL_LIST_OBJECTS=false, which may affect callers expecting public buckets to allow unauthenticated listing. Also refactors request header middleware and adds new validation/tests, so any header-setting regressions would surface at runtime.Overview
Bucket creation now disables directory listing by default by always sending
TigrisHeaders.ACL_LIST_OBJECTS=falseduringcreateBucket, including foraccess: 'public'buckets.The header-setting logic in
createBucketis consolidated into a single middleware (tier/consistency/regions/locations/snapshot/fork headers), and a new validation error is returned whensourceBucketSnapshotis provided withoutsourceBucketName.Adds
bucket-create.integration.test.tsto cover basic creation/listing, public bucket non-listability (expects403on unauthenticatedListObjects), snapshot-enabled buckets, fork creation, location variants, combined options, and validation failures.Written by Cursor Bugbot for commit fd890db. This will update automatically on new commits. Configure here.