Bug #12886
closedRGW Swift API: X-Object-Manifest cannot to be added through POST
0%
Description
$ curl -i "$publicURL/cont/obj" -X POST -H "X-Object-Manifest: bla" -H "X-Auth-Token: $token"
HTTP/1.1 202 Accepted
Content-Length: 0
Accept-Ranges: bytes
X-Trans-Id: tx000000000000000000729-0055e49f7f-101c-default
Content-type: text/plain; charset=utf-8
Date: Mon, 31 Aug 2015 18:39:59 GMT
$ curl -i "$publicURL/cont/obj" -X HEAD -H "X-Auth-Token: $token"
HTTP/1.1 200 OK
Content-Length: 2
Accept-Ranges: bytes
Last-Modified: Mon, 31 Aug 2015 18:39:59 GMT
X-Timestamp: 1441046399.00000
etag: 444bcb3a3fcf8389296c49467f27e1d6
X-Trans-Id: tx00000000000000000072a-0055e49f84-101c-default
Content-type: application/x-www-form-urlencoded
Date: Mon, 31 Aug 2015 18:40:04 GMT
Swift does support that:
$ curl -i "$publicURL/cont/obj" -X POST -H "X-Object-Manifest: bla" -H "X-Auth-Token: $token"
HTTP/1.1 202 Accepted
Content-Length: 76
Content-Type: text/html; charset=UTF-8
X-Trans-Id: txb3ac0c10c1a74c7e9b195-0055e49efd
Date: Mon, 31 Aug 2015 18:37:49 GMT<html><h1>Accepted</h1><p>The request is accepted for processing.</p></html>
$ curl -i "$publicURL/cont/obj" -X HEAD -H "X-Auth-Token: $token"
HTTP/1.1 500 Internal Error
Content-Length: 17
Content-Type: text/plain
X-Trans-Id: txe6025e546dc2488483476-0055e49f0e
Date: Mon, 31 Aug 2015 18:38:06 GMT
500 is an expected behaviour in this exact case (wrong path in value of X-Object-Manifest header).
Updated by Radoslaw Zarzynski over 8 years ago
- Status changed from New to In Progress
- Assignee set to Radoslaw Zarzynski
I'm working on that.
Updated by Radoslaw Zarzynski over 8 years ago
- Status changed from In Progress to Fix Under Review
Pull request: https://github.com/ceph/ceph/pull/5741.
Updated by Casey Bodley about 4 years ago
- Status changed from Fix Under Review to Resolved