CLDSRV-909: Reject CopyObject when source exceeds 5 GiB (backport)#6233
CLDSRV-909: Reject CopyObject when source exceeds 5 GiB (backport)#6233tcarmet wants to merge 4 commits into
Conversation
Hello tcarmet,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
❌ 2 Tests Failed:
View the top 1 failed test(s) by shortest run time
View the full list of 1 ❄️ flaky test(s)
To view more test analytics, go to the Test Analytics Dashboard |
|
/create_integration_branches |
ConflictA conflict has been raised during the creation of I have not created the integration branch. Here are the steps to resolve this conflict: git fetch
git checkout -B w/9.4/bugfix/CLDSRV-909-enforce-copyobject-source-size-limit origin/development/9.4
git merge origin/bugfix/CLDSRV-909-enforce-copyobject-source-size-limit
# <intense conflict resolution>
git commit
git push -u origin w/9.4/bugfix/CLDSRV-909-enforce-copyobject-source-size-limitThe following options are set: create_integration_branches |
Backport of #6177 to
development/9.3.Align cloudserver's CopyObject with the AWS S3 contract by rejecting requests whose source object exceeds 5 GiB. AWS S3 returns HTTP 400
InvalidRequest("The specified copy source is larger than the maximum allowable size for a copy source: 5368709120") and expects clients to use the multipart copy flow instead; cloudserver previously accepted these requests. ThebypassMaxPutObjectSizeflag still overrides the limit, matching the PutObject behavior.The first commit is a prettier-only reformat of the two touched files and can be skipped during review; the actual change lives in the three cherry-picked commits.