Cyberduck Mountain Duck CLI

#10644 closed defect (thirdparty)

Preserve the timestamp with Jfrog

Reported by: chhinf Owned by: dkocher
Priority: normal Milestone: 7.0
Component: webdav Version: 6.9.3
Severity: normal Keywords:
Cc: Architecture: Intel
Platform:

Description

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.

Change History (6)

comment:1 Changed on Mar 9, 2019 at 8:43:06 PM by dkocher

What protocol are you using?

comment:2 Changed on Mar 9, 2019 at 8:43:16 PM by dkocher

  • Milestone changed from 7.0 to 6.9.5
  • Priority changed from highest to normal
  • Severity changed from blocker to normal

comment:3 Changed on Mar 11, 2019 at 1:08:18 PM by chhinf

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.

comment:4 Changed on Mar 11, 2019 at 1:19:19 PM by dkocher

  • Component changed from core to webdav
  • Owner set to dkocher

comment:5 Changed on Mar 11, 2019 at 1:21:51 PM by dkocher

  • Resolution set to thirdparty
  • Status changed from new to closed
  • Summary changed from Why I can not preserve the timestamp from Windows Explorer to Cyberduck to Preserve the timestamp with Jfrog

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.

comment:6 Changed on Jun 4, 2019 at 2:20:54 PM by dkocher

  • Milestone changed from 6.9.5 to 7.0

Ticket retargeted after milestone deleted

Note: See TracTickets for help on using tickets.