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
Interoperability with nginx #6767
Comments
An account for testing would help to resolve this issue. |
Hi, thanks for your quick response, I've made an account in server so you can test, details follows:
When you login you will see a welcome.txt file. Let me know if you have any problems login in, or if you need further nginx debug on the server side.. Regards, |
Replying to [comment:2 nelson]: I get the following failure which indicates WebDAV is not setup for this virtual host.
|
Hi, when do you get that failure? I can successfully login in with cyberduck.. |
I can now successfully connect over HTTPS. |
I finally did some testing uploading a directory with files but couldn't see any issues. What specifically does go wrong? |
Hi, indeed I've also tested that uploading files and folders works well, what is still failing for me is the "overwriting files" operation. If I upload a file that already exists the overwrite dialog pops up but when performed the action the file didn't got overwrited and an error dialog pops up, I tried to debug the issue server side and nginx is not writing any error or access log message when the error dialog pops up in cyberduck, which it seems to me as it cyberduck didn't sent that call. The same problem happens when using "Edit file with.." action to edit a file with a text editor, as when you save in the editor cyberduck tries to upload the file and fails to overwrite. I hope you can reproduce this issue with the test server I set up. Thanks! |
Replying to [comment:8 nelson]:
I get a |
Replying to [comment:9 dkocher]:
Yes, that was a segmentation fault in nginx, see http://trac.nginx.org/nginx/ticket/311#comment:1 The segfault is fixed in nginx-1.2.6+ and the dav upload problem real fix in nginx-1.3.9+ Anyway, as distros are only packaging stable nginx versions 1.2.x and the dav upload erratic problem is fixed in 1.3.9, can I ask if cyberduck can provide an option to disable sending the Expect: 100-continue header ? this way nginx stable versions 1.2.x could be used as reliable dav servers becuase handling the Expect: header was causing the issue. Basically an option to make http://haacked.com/archive/2004/05/15/http-web-request-expect-100-continue.aspx http://alihamdar.com/2010/06/19/expect-100-continue/ http://msdn.microsoft.com/en-us/library/system.net.servicepoint.expect100continue.aspx |
Replying to [comment:10 nelson]:
You can use the hidden option
|
Thanks very much for that!! Btw where do I write that command? I've search for it and it seems a Mac OS X configuration command, but I'm running Cyberduck on windows and running that command in the windows shell gives me "unrecognized command" error. Regards, |
Replying to [comment:12 nelson]:
Please refer to Hidden configuration options. |
Replying to [comment:10 nelson]:
Thanks for the reference. |
Replying to [comment:13 dkocher]:
Thanks for the info! unfortunately it seems Cyberduck is not obeying that config option, I write it as the help says but Cyberduck continues sending Expect header and so nginx failing. I'm sure I have written it right, see:
It seems to me like a bug in Cyberduck windows version reading that config.. :-( Regards, |
Replying to [comment:15 nelson]:
You must use the latest beta build for this setting to work. |
Replying to [comment:16 dkocher]:
Thanks, indeed I've updated to latest beta 4.2.2(10748) and the That said, deleting a file causes cyberduck to crash, and I clicked the dialog to send you the crash trace along. |
Well, it also crashes just when trying to exit the application in "File -> Exit" menu. I updated through Beta channel from within the application. |
Hi, I have an nginx web server to host my webpages, nginx has webdav built-in support so I configured it to upload my www content to my site through webdav, I configured it on https protocol + basic authentication for security. Cyberduck is able to login succesfully, but has erratic behaviour when performing different operations, mainly:
If you're interested in improving webdav support with nginx servers I would happily create a user account on my server for you to test.
Regards,
The text was updated successfully, but these errors were encountered: