We are having the same problem with version 4.3.1, but not the previous version.
Make sure your webserver provides something like DirectoryIndex for WebDAV directory. In our case, we had an additional problem, because although we configured Apache to provide a DirectoryIndex, we were using the directive 'SetHandler default-handler' which overrode the DirectoryIndex directive. For us, the solution was to remove the 'SetHandler default-handler' directive.
Apparently the new Cyuberduck version begins the connection with the HEAD command, as shown in the error_message.jpg file from the first poster (the previous CyberDuck version used the PROPFIND command). If the web server is not configured to provide DirectoryIndex with a directory, the web server will return a NOT FOUND for the HEAD command, and the new Cyberduck will fail.
I can connect webdav server (tomcat) using cyberduck 4.2.1
but connect fail using the same setting in 4.3.1
error message.jpg(95.7 KiB)
The text was updated successfully, but these errors were encountered: