Bug #5843
closedswift api: x-container-meta-{key} should not be allowed on an object
0%
Description
Using 'x-container-meta-{key}' to update object custom metadata should be disallowed, since it's supposed to be used to update container metadata.
$ curl -i -XPOST -H "X-Auth-Token: <token>" -H "X-Container-Meta-Container: Should Fail, but works" -H "X-Object-Meta-Object: Works" https:/server/swift/v1/test-object-custom-metadata/object-custom-metadata
HTTP/1.1 202 Accepted
Date: Thu, 01 Aug 2013 23:42:10 GMT
Server: Apache
Vary: Accept-Encoding
Transfer-Encoding: chunked
Content-Type: text/plain; charset=utf-8
$ curl -i -XHEAD -H "X-Auth-Token: <token>" https://server/swift/v1/test-object-custom-metadata/object-custom-metadata
HTTP/1.1 200 OK
Date: Thu, 01 Aug 2013 23:42:23 GMT
Server: Apache
Accept-Ranges: bytes
Last-Modified: Thu, 01 Aug 2013 23:42:10 GMT
etag: 09108ba8f5ef7d88c9db99cd3ff2752b
X-Object-Meta-container: Should Fail, but works
X-Object-Meta-object: Works
Content-Length: 16
Content-Type: binary/octet-stream
Updated by Sage Weil over 10 years ago
- Status changed from New to 4
is this causing actual problems? it may be easier to leave it how it is.
Updated by Alexandre Marangone over 10 years ago
It came from a customer, after discussions it is not causing any issue at all. We can leave it how it is.