Closed briancurtin closed 9 years ago
FWIW, ob.fetch(include_meta=True) does properly return metadata
Curious to see a code snippet.
This gist works for me.
REQ: curl -i -X HEAD -H 'X-Auth-Project-Id: 123456' -H 'User-Agent: pyrax/1.9.3' -H 'Accept: application/json' -H 'X-Auth-Token: abcd' https://storage101.ord1.clouddrive.com/v1/xxx/xyz/test.txt
RESP: <Response [200]>
{'content-length': '13', 'accept-ranges': 'bytes', 'x-object-meta-m1': '1429938184', 'last-modified': 'Fri, 06 Mar 2015 00:03:55 GMT', 'etag': '8c3c1a60b5c10f3faacd15ae3b1db6fb', 'x-timestamp': '1425600234.31237', 'x-trans-id': 'tx0c9d18fff68b4020af8df-0054f8f10eord1', 'date': 'Fri, 06 Mar 2015 00:13:02 GMT', 'content-type': 'text/plain'}
{'m1': '1429938184'}
Never mind. get_metadata - either on containers or objects - only returns user-specified metadata, while I was thinking it returns all metadata.
With debug logging enabled, you can see that the proper request and response are happening, but the response isn't hooked up to the object.
That empty dict at the end is the return value and the dict above it is the metadata showing up from the logging.