New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
404 response for HEAD request #7187
Comments
Please post the transcript from the log drawer (Ctrl-L). |
I don't have any idea what a log drawer is. If Cyberduck has a log, I don't know about it (but would like to). Examples of the access log from the Apache web server are as follows:
|
Replying to [comment:2 billhuber01]:
Yes, there is a log drawer where you can find the connection transcript. |
Replying to [comment:2 billhuber01]:
We have changed the check of valid authentication credentials in 4.3 that we first try a |
I still don't know where the content of the log drawer is. The only description is the following: Choose View → Toggle Log Drawer (⌘-L) to open the log drawer. Events are only logged once the drawer is open. Yes, I can click on View and Toggle Log Drawer, but I have no idea where any log output is. Where is it and exactly how do I look at it? Thank you. |
I have installed nuxeo-cap-5.6-tomcat locally for testing and can login with no issues.
I suppose this is a configuration issue. |
Here's a work-around for Apache, and a suggestion for Cyberduck. Cyberduck version pre-4.3 would open a connection using the OPTIONS method on the directory. Apache worked well with that. Newer Cyberduck versions open a connection using the HEAD method on a directory, which leads to problem with some Apache installations. If Apache is configured to provide an index file for the directory (using the Apache DirectoryIndex directive or the Options +Index directive) then a code 200 by the HEAD method on a direcotry, and Cyberduck 4.3+ works fine. If no index file is server for a directory, then some Apache versions/configurations return a 404 code, which Cyberduck 4.3+ takes as a failure. Other Apache versions/configurations return a 403 code, which Cyberduck 4.3+ handles fine. If your Apache has the problem and returns code 404, which you can see in this Apache access log entry, Also, it looks like Cyberduck could be modified to work again with such Apache installations by either reverting to the OPTIONS method when opening a connection, or handling the 404 return code the same way it handles the 403 return code. |
We have been using Cyberduck 4.2.1 and 4.2.2 just fine with our WebDAV server. Upon upgrading to Cyberduck 4.3, we are unable to open a connection the our WebDAV server. In return we get a 404 error, not found.
I have actually tried this on two different WebDAV servers: the Apache Web Server and one included as part of Nuxeo. They both failed. The returned output on the failed Cyberduck screen is shown in the attached screen shot.
Needless to say, this is a seriously blocking problem unless there is some way to configure Cyberduck in 4.3 to work around the problem. Is there anything like that?
Attachments
Screen Shot 2013-05-02 at 15.00.57.png
(61.9 KiB)cyberduck_connect_problem.doc
(37.0 KiB)The text was updated successfully, but these errors were encountered: