Actions
Bug #20395
closedrgw: X-Account-Access-Control of Swift API should be omitted if there is no ACL
% Done:
0%
Source:
Tags:
Backport:
kraken
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
At the moment we're are sending an empty JSON object in such situation:
HTTP/1.1 204 No Content.
X-Timestamp: 1498224414.24035.
X-Account-Container-Count: 0.
X-Account-Object-Count: 0.
X-Account-Bytes-Used: 0.
X-Account-Bytes-Used-Actual: 0.
X-Account-Access-Control: {}.
X-Trans-Id: tx0000000000000000000b7-00594d171e-1060-default.
X-Openstack-Request-Id: tx0000000000000000000b7-00594d171e-1060-default.
Accept-Ranges: bytes.
Content-Type: text/plain; charset=utf-8.
Date: Fri, 23 Jun 2017 13:26:54 GMT.
.
Updated by Radoslaw Zarzynski almost 7 years ago
- Status changed from New to In Progress
Updated by Radoslaw Zarzynski almost 7 years ago
- Status changed from In Progress to Fix Under Review
Updated by Casey Bodley almost 7 years ago
pr merged - does it need backport? if not, please resolve
Updated by Radoslaw Zarzynski over 6 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to kraken
Updated by Nathan Cutler over 6 years ago
- Copied to Backport #20831: kraken: rgw: X-Account-Access-Control of Swift API should be omitted if there is no ACL added
Updated by Nathan Cutler over 6 years ago
- Status changed from Pending Backport to Resolved
Actions