Cyberduck Mountain Duck CLI

Opened on Feb 1, 2019 at 2:30:26 PM

Closed on Nov 28, 2019 at 9:49:05 AM

#10593 closed defect (worksforme)

Strange behavior with WebDav on QNAP NAS

Reported by: savonarola Owned by:
Priority: normal Milestone: 7.1.1
Component: webdav Version: 6.9.0
Severity: normal Keywords: qnap webdav
Cc: Architecture: Intel
Platform: macOS 10.14

Description

I have a strange behavior when I connect with CyberDuck and MountainDuck to my QNAP NAS via WebDav.

Both programs connect but create an empty folder with the same name as the folder I access. Even when I access sub-folders. Every time I find an empty folder with the same name of the folder in which I am.

CyberDuck gives me an error when I try to access that folder while MountainDuck gives me access but I find it empty.

I tried to connect to a simple WebDav server created on a Centos 7 server and this behavior does not occur.

Do you have any advice?

Change History (5)

comment:1 follow-up: Changed on Mar 4, 2019 at 7:18:47 PM by mhuyck

I am experiencing very similar behavior (suggesting the same underlying cause) when I try to use the duck command line tool, which fails for me when I try to use the --synchronize option.

Steps to reproduce:

  1. Start with a WebDAV server containing a directory of files and a matching local directory of files
  2. Attempt to synchronize them (nothing should happen if they really do match) using the command: duck -v --synchronize davs://user@host.example.com/path/ ~/local/path/
  3. The verbose output shows a series of HTTP headers that seem to indicate that duck is traversing the files on the WebDAV server in breadth-first fashion, which succeeds until descending into the first directory (let's say it's ...host.example.com/path/dir1/).
  4. While traversing the first directory, the breadth-first scan continues through all the files in dir1/ until it comes to the end and tries a PROPFIND on an imaginary file called dir1/dir1/.
  5. The WebDAV server (rightly) responds with HTTP/1.1 404 Not Found, at which point duck complains with the message Listing directory dir1 failed. Unexpected response (404 Not Found). Please contact your web hosting service provider for assistance.

I hope this helps to identify the problematic code. Let me know if I can assist further.

Last edited on Mar 4, 2019 at 7:20:09 PM by mhuyck (previous) (diff)

comment:2 in reply to: ↑ 1 Changed on Mar 4, 2019 at 7:30:04 PM by mhuyck

I should add that the output of duck --version on my Mac is Cyberduck 6.9.4 (30164). I am running Mojave version 10.14.3 (18D109).

My WebDAV server is running on a Synology NAS, so this issue is not isolated to QNAP.

comment:3 Changed on Oct 29, 2019 at 9:44:58 AM by dkocher

The resource itself should be ignored from the PROPFIND reply. Is this still reproducible in the latest version?

comment:4 Changed on Oct 30, 2019 at 10:00:01 AM by savonarola

The issue is no more present (Mountain Duck 3.2.1 and Cyberduck 7.1.1).

Last edited on Oct 30, 2019 at 10:01:09 AM by savonarola (previous) (diff)

comment:5 Changed on Nov 28, 2019 at 9:49:05 AM by dkocher

  • Milestone set to 7.1.1
  • Resolution set to worksforme
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.