Method not allowed for HEAD request

[cyberduck]

4f1ef7b created the issue

I can connect webdav server (tomcat) using cyberduck 4.2.1
but connect fail using the same setting in 4.3.1

---

Attachments

• error message.jpg (95.7 KiB)
• setting.jpg (88.1 KiB)

[cyberduck]

@dkocher commented

Pasting previous comment here by Jon Rifkin:

We are having the same problem with version 4.3.1, but not the previous version.

WORKAROUND

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.

CAUSE

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.

[cyberduck]

@dkocher commented

Same issue reported in #7203.

[cyberduck]

@dkocher commented

See also #7187.

[cyberduck]

@dkocher commented

As noted by the previous comment, authentication handling in 4.3 was changed. See #7139. A HEAD request is issued to check access permissions to the resource.

[cyberduck]

@dkocher commented

We will implement a workaround for 404 and 405 errors.

[cyberduck]

@dkocher commented

In aa31725.

[cyberduck]

@dkocher commented

#7313, #7290, #7219, #7203, #7306, #7266 closed as duplicates.

[cyberduck]

@dkocher commented

#7342 closed as duplicate.

[cyberduck]

@dkocher commented

#7346 closed as duplicate.