Project

General

Profile

Actions
Copy link

Bug #20395

closed

rgw: X-Account-Access-Control of Swift API should be omitted if there is no ACL

Added by Radoslaw Zarzynski almost 7 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Radoslaw Zarzynski
Target version:
-
% 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.
.

Related issues 1 (0 open — 1 closed)

Copied to rgw - Backport #20831: kraken: rgw: X-Account-Access-Control of Swift API should be omitted if there is no ACLRejectedActions
Actions
Copy link

Also available in: Atom PDF