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

Jump to bottom

Preserve the timestamp with Jfrog #10644

Closed
cyberduck opened this issue Mar 6, 2019 · 4 comments
Closed

Preserve the timestamp with Jfrog #10644

cyberduck opened this issue Mar 6, 2019 · 4 comments
Assignees
@dkocher
Labels
bug thirdparty Issue caused by third party webdav WebDAV Protocol Implementation
Milestone
7.0

Comments

@cyberduck
Copy link
Collaborator

3aa26eb created the issue

I am accessing the Artifactory via Cyberduck.
I had to configured Cyberduck to preserve the timestamp of download and upload. When I tried uploaded the zip file, it instead updated the timestamp to current date and not the timestamp of the source file.
@cyberduck
Copy link
Collaborator Author

@dkocher commented

What protocol are you using?

@cyberduck
Copy link
Collaborator Author

3aa26eb commented

When I setup the cyber duck, I used WebDAV protocol. In addition, I selected the option in Download and Upload to "preversed the timestamp" for Jfrog. I tested 2 way

  1. using the "upload" option in cyber duck
  2. drag form Windows Explorer to cyber duck

The artifacts was uploaded but the timstamp was updated to current date and not preversed the source timestamp.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We depend on custom attributes that are set to preserve the timestamp as there is no standard for saving modification times in WebDAV. The target system may display a different timestamp and in Cyberduck you will only see the correct timestamp if the server correctly returns custom attributes set in the non default namespace.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Ticket retargeted after milestone deleted

@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.
Assignees

@dkocher dkocher

Labels
bug thirdparty Issue caused by third party webdav WebDAV Protocol Implementation
Projects
None yet
Milestone
7.0
Development

No branches or pull requests
2 participants
@dkocher @cyberduck