You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
REST responses directly from s3 do not return empty tags, but REST responses from versitygw do. While not a serious issue, optional XML tags that aren't set shouldn't be returned.
For example, versitygw returns this when there is no object lock config rule:
Send for both direct (s3.amazonaws.com) and versitygw.
Compare the two. Note the empty tags after sending to versitygw.
Expected behavior
versitygw doesn't return unnecessary optional XML tags.
Server Version
Version : v1.0.7
Build : b7291c3
BuildTime: 2024-09-25_08:28:23PM
Darwin Lukes-MacBook-Pro.local 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:25 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6030 arm64
The text was updated successfully, but these errors were encountered:
Describe the bug
REST responses directly from s3 do not return empty tags, but REST responses from versitygw do. While not a serious issue, optional XML tags that aren't set shouldn't be returned.
For example, versitygw returns this when there is no object lock config rule:
s3 returns this:
Since
Rule
is an optional parameter and isn't set.To Reproduce
Expected behavior
versitygw doesn't return unnecessary optional XML tags.
Server Version
Version : v1.0.7
Build : b7291c3
BuildTime: 2024-09-25_08:28:23PM
Darwin Lukes-MacBook-Pro.local 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:25 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6030 arm64
The text was updated successfully, but these errors were encountered: