Inconsistencies between CLI list command and actual File Object

[Antonio ElPepe Segoviano]

I've been dealing with some file issues for some time around and I don't seem to find any resource that could help me with the actual updated listing of my storage. I need to be able to handle all files in a batch manner, but the CLI is giving me some results, while a direct http request gives me another result, and even more, sometimes the actual Rackspace portal gives me another different result.

In short, I have this questions:

why does this works...,

$  (local-image-test) $ curl -I -X HEAD $CDN_CONTAINER_URL/14981.dzi
HTTP/1.1 200 OK
Content-Length: 206
Accept-Ranges: bytes
Last-Modified: Fri, 18 May 2018 01:14:57 GMT
ETag: ac2fff591f4ff3e6cbbdcc621056b837
X-Timestamp: 1526606096.23477
Access-Control-Allow-Origin: *
Content-Type: application/octet-stream
X-Trans-Id: txf28492e849f547aaa68f2-005afe2991dfw1
Cache-Control: public, max-age=992
Expires: Fri, 18 May 2018 01:33:37 GMT
Date: Fri, 18 May 2018 01:17:05 GMT
Connection: keep-alive

while this does not?

$  (local-image-test) $ rack files object list --container $CDN_CONTAINER --no-header | egrep '\.dzi'
1146.dzi			204		application/octet-stream	2018-05-15T07:33:52.479170
11461.dzi			206		application/octet-stream	2018-05-15T07:35:09.913890
11463.dzi			206		application/octet-stream	2018-05-15T07:36:04.791320

Does the CLI connects through some cache? Is this some kind of issue?

Thanks.