@Rajaneesh: 4096 is the default size, but it might be different - depending on the setting in swift.conf.
If you execute the HEAD to get the current size of the metadata entry the request might use an older version of the account/container database with a lower number of metadata entries, but the actual metadata entry might be higher.
@John: agreed, it's not a serious security issue. But then I think it might be a good idea to fix this before making the bug public? Otherwise people might try to abuse the current behavior?
@Rajaneesh: 4096 is the default size, but it might be different - depending on the setting in swift.conf.
If you execute the HEAD to get the current size of the metadata entry the request might use an older version of the account/container database with a lower number of metadata entries, but the actual metadata entry might be higher.
@John: agreed, it's not a serious security issue. But then I think it might be a good idea to fix this before making the bug public? Otherwise people might try to abuse the current behavior?