You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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:
Start with a WebDAV server containing a directory of files and a matching local directory of files
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/
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/).
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/.
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.
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?
The text was updated successfully, but these errors were encountered: