mirror of
https://github.com/versity/versitygw.git
synced 2026-07-07 08:36:42 +00:00
Ben McClelland
9db2c9c702
When versitygw serves files that were placed on the filesystem outside of the gateway, those files have no stored etag attribute and are served with an empty ETag. This causes problems for S3 clients that rely on ETags being non empty. The new --default-etag flag (VGW_DEFAULT_ETAG) lets operators specify a fallback ETag value returned for any object that lacks a stored etag attribute, making pre-existing filesystem data behave more predictably under S3 workloads without requiring a metadata migration.