Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modified column shows "Unknown" for all files and folders #10446

Closed
cyberduck opened this issue Aug 29, 2018 · 8 comments
Closed

Modified column shows "Unknown" for all files and folders #10446

cyberduck opened this issue Aug 29, 2018 · 8 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Aug 29, 2018

0690414 created the issue

The "Modified" (timestamp) column for all containers and file objects (and virtual folders) shows as "Unknown" for Rackspace CloudFiles (OpenStack) in Cyberduck v6.7.0. I've confirmed the same results on two different Rackspace CloudFiles accounts. I've confirmed I do see modified timestamps as expected on an sftp connection to a server so the problem may be limited to when using Rackspace CloudFiles (OpenStack). This problem started recently since I use this tool often to sort files by their modified date and now I can't.

Log transcript from "Update" at root level is attached.


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 3, 2018

@dkocher commented

Could you please file a bug report with Rackspace that their API does no longer include last_modified in their response when listing objects.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 4, 2018

0690414 commented

Is there an example api test you used to determined this so I can provide it for a complete report documentation? (i.e. did you confirm this with a curl script or something?) Can you provide it here and I will submit the Rackspace bug report?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 4, 2018

0690414 commented

I ran a curl test myself just now for a particular file object and I get a Last-Modified field back.
Not sure if the url used makes a difference, I think Rackspace has multiple endpoint possibilities with varying versions, etc.

I tried a particular file object test using

curl -X HEAD -D - -H "X-Auth-Token: XXXX" https://storage101.dfw1.clouddrive.com/v1/MossoCloudFS_XXXX/path/to/file

And I get

HTTP/1.1 200 OK 
Content-Length: 2065 
Accept-Ranges: bytes 
Last-Modified: Tue, 19 Jan 2016 01:19:58 GMT 
Etag: 7c96XXXX786e971a9ee7ddf0769033 
X-Timestamp: 1453166397.26005 
Content-Type: application/octet-stream 
X-Trans-Id: tx968abXXXX6144d9f94efc-005b8dd00cdfw1 
Date: Tue, 04 Sep 2018 00:21:33 GMT

Notice Last-Modified exists above.

Are you getting different results?

If so, is it a different url that is used? Different something else?

Can you provide an equivalent test that has the Last-Modified omitted if you think this is a bug on the Rackspace?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 4, 2018

@dkocher commented

We do a object listing using a GET request for the container like

curl -X GET -D - -H "X-Auth-Token: xxxx" "https://storage101.dfw1.clouddrive.com/v1/MossoCloudFS_xxxx/cdn.cyberduck.ch?format=xml&prefix=&limit=1&delimiter=%2F"

All objects should contain a last_modifiedin the returned XML document. My first test shows this is actually the case. We will look into it.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 4, 2018

@dkocher commented

It looks like the timestamp format returned is no longer RFC 1123 but ISO 8601. We will implement a workaround.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 4, 2018

@dkocher commented

In dc1115d.

Loading

@cyberduck cyberduck closed this Sep 4, 2018
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 20, 2018

@dkocher commented

Milestone renamed

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 9, 2018

@dkocher commented

Related issue in #10489.

Loading

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants