We use Cyberduck to access the WebDAV server on the Alfresco's Enterprise Content Management solution (see http://www.alfresco.com).
It works really well, unless a file in a directory is locked by Alfresco. In that case, the listing of that directory is blank in Cyberduck. We've run traces of the interaction with Wireshark, and it appears that if the PROPFIND from the server returns results similar to the following on any single file in a directory, Cyberduck will refuse to list all of the contents of that directory. By "refuse to list" I mean that the directory appears to have nothing in it when you view it in Cyberduck, even if you upload a new file using Cyberduck. No error message is displayed or logged.
I have been working on Sardine as a replacement for the current WebDAV protocol implementation in Cyberduck. I'll let you know when a snapshot build is ready for testing and we will debug further then if the issue is still open.
Thanks for the update. I just tried it with version 4.0.3 (8692), and I'm still seeing the issue.
There is a change, though: It shows a little red do-not-enter symbol on an affected directory sometimes. It sort of comes and goes when I try to double-click into the folder--sometimes it shows up, sometimes it doesn't. A portion of the times when it's showing, I can't open the directory, but sometimes I can.
When I can open the folder, unfortunately I still don't see any contents.
BTW, We're actually hoping that it'll end up working like Cadaver/Windows/Mac/Transmit, in that the user will be allowed to click into the folder, and will see the contents of that folder....from what (little) we've been able to establish, that's what should be happening.
Thanks again for your work on this, and please do let me know if there's anything else I can do to help!
Just a quick note to say thanks for your help on this. You were right--it was a bug in Alfresco.
Some details, in case anyone else runs across this:
It turns out that this mal-formed XML was due to a bug in Alfresco version 3.3.3 (and possibly prior to that). Upgrading to 3.3.4 or later fixes the bug, but it may be necessary--it was in my case--to use a script to go through and manually delete the locks that were created prior to version 3.3.4.