[Cyberduck-trac] [Cyberduck] #10593: Strange behavior with WebDav on QNAP NAS

[Cyberduck]

#10593: Strange behavior with WebDav on QNAP NAS
-------------------------+----------------------
 Reporter:  savonarola   |         Owner:
     Type:  defect       |        Status:  new
 Priority:  normal       |     Milestone:
Component:  webdav       |       Version:  6.9.0
 Severity:  normal       |    Resolution:
 Keywords:  qnap webdav  |  Architecture:  Intel
 Platform:  macOS 10.14  |
-------------------------+----------------------

Comment (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.

--
Ticket URL: <https://trac.cyberduck.io/ticket/10593#comment:1>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows