Bug #14903
rgw: limit=0 parameter is wrongly handled during Swift acccount listing
0%
Description
Swift:
$ curl -i "$publicURL/?limit=0" -X GET -H "X-Auth-Token: $token"
HTTP/1.1 204 No Content
Content-Length: 0
X-Account-Object-Count: 17
X-Timestamp: 1444053537.48538
X-Account-Bytes-Used: 576
X-Account-Container-Count: 10
Content-Type: text/plain; charset=utf-8
Accept-Ranges: bytes
X-Trans-Id: tx0aecbeef851844afae9e4-0056d07514
Date: Fri, 26 Feb 2016 15:53:56 GMT
rgw:
$ curl -i "$publicURL/?limit=0" -X GET -H "X-Auth-Token: $token"
HTTP/1.1 200 OK
X-Timestamp: 1456488062.31655
X-Account-Container-Count: 3
X-Account-Object-Count: 0
X-Account-Bytes-Used: 0
X-Account-Bytes-Used-Actual: 0
X-Trans-Id: tx000000000000000000014-0056d03e7e-1018-default
Content-Length: 20
Accept-Ranges: bytes
Content-Type: text/plain; charset=utf-8
Date: Fri, 26 Feb 2016 12:01:02 GMTcont10
cont12
cont15
Associated revisions
rgw: fix wrong handling of limit=0 during listing of Swift account.
Fixes: #14903
Signed-off-by: Radoslaw Zarzynski <rzarzynski@mirantis.com>
History
#1 Updated by Radoslaw Zarzynski about 8 years ago
- Status changed from New to In Progress
- Assignee set to Radoslaw Zarzynski
#2 Updated by Radoslaw Zarzynski about 8 years ago
- Status changed from In Progress to Fix Under Review
Pull request: https://github.com/ceph/ceph/pull/7821.
#3 Updated by Daniel Gryniewicz about 4 years ago
- Status changed from Fix Under Review to Resolved