Customer Portal

Get Involved. Join the Conversation.

Topic

    david fulton
    Overview of your WebDAV options by OS/VendorAnswered
    Topic posted December 12, 2008 by david fultonBronze Trophy: 5,000+ Points, last edited November 2, 2012 
    18655 Views, 24 Comments
    Title:
    Overview of your WebDAV options by OS/Vendor
    Content:


    Hello everyone,



    One of the questions we get most often is about WebDAV support for Dreamweaver, particularly given Adobe's rather patchy implementation of the protocol in DreamWeaver. We wanted to give you some insight into why we selected WebDAV as a file transfer protocol, what options are out there for you to use, and give you some insight into the enhancements coming to that component. Also, we would like you to use this thread to give us some insight into how you use WebDAV, and the tools etc that you find useful.



    Why did we select WebDAV?





    HTTP Based

    WebDAV is more accessible to corporate clients because it is HTTP based.  It doesn't require additional holes in the firewall and the protocol is compatible with proxies, even if some of its clients aren’t. WebDAV works well with our hosting infrastructure because it’s HTTP-based. Additionally, handling security for an HTTP-based protocol is simple: run it over SSL.



    Open Standard

    WebDAV is an Internet standard with many clients, and even the commercial solutions are reasonably priced.



    Level of Support

    While other HTTP-based file-authoring protocols exist, none is as widely supported as WebDAV.



    One of the challenges that WebDAV users are likely to face is the differences between vendors (and even OS systems) as to the flavor of WebDAV that they have implemented and supported. We've compiled the attached document to give you an idea of your options here and to highlight some of the issues that you'll need to be aware of in choosing your WebDAV option. Note that the attached document is fairly old at this point, but for those of you sticking to old OS's the observations and recommendations remain current. Our Current Recommendation (below) references the current recommendation (for 2012) and the reasons why we like it.



    Current Recommendations

    Our current (as of Fall 2012) recommendation is a solution called CyberDuck. Cyberduck is a donationware app that is multi-platform (Mac + PC) and pretty nippy when it comes down to transfer speed. Our devs have been using it for a while now and have been impressed. We like it more than WebDrive (some of WebDrive's caching can irritate when you are making rapid queries/uploads to a file server) and initial feedback is that the solution is robust on both Mac and PC platforms. Worth a look and let us know on this thread or the recent update thread what you think of it.



     

    Best Comment

    Christopher Tarabochia

    This information is now provided in the Developer Documentation under the Getting Started section

    Comment

    • Lorna Rickett

      We have to use 4.4.3 for Windows, too (same reasons).

    • Luis Melo

      Hello,

      I have updated my version to 4.6.4 and it still did not work. I kept getting the same error message and unable to upload files.

      Then downgraded to version 4.4.3 but am getting the same thing.

      This is really crucial and a show stopper.

    • Luis Melo

      I have checked with some of my colleagues that version 4.4.3, 4.5.2 and 4.6.4 is working for them. Some in Windows 7 Pro and others in Windows 8 Pro.

      I am in Windows 8.1 Pro and no version works for me. Keep getting the same error when trying to upload files 

    • Rajan Davis

      Hi Luis,

      I would strongly advise opening a ticket with Cyberduck regarding your issues, there seems to be more information there about issues  with their webdav client than here (which is to be expected, but it would be nice if there was an answer telling people which specific version of the client to use).

      Also, can you please show us what error you are getting? I would try to use Window's native webdav client and see if that works first, you might be inputting in values incorrectly. There were a few post on the RightNow community about changing some settings in Cyberduck that might help. 

      Edit: There might be an issue with Windows 8.1 using SSLv2

    • Robert Lund

      I did a little investigation into this. Is the error that you are seeing a 301 - Moved Permanently error? If it is, are you by chance connected to WebDAV using http instead of https?

      Looking through the Cyberduck changelogs it looks like in version 4.4.4 they introduced a new option around following redirects on PUT requests. See ticket #6586. This is exactly what is happening when you try to upload a file to your site over an non-https connection. A PUT request with your file is made, and a 301 redirect is given as a response. 

      To fix this try connecting to your site through https. If you are still seeing errors, would you mind posting a screenshot or the text of the error?

    • Bastiaan van der Kooij

      I am a little suprised to see that WinSCP is not listed here. After all the horror with cyberduck, webdrive, netdrive etc...

      This client is just plain perfect for working with CP, fast reliable never any issue. What I typically do is copy the whole customer folder to my local pc and in WinSCP sync the customer folder with my local customer folder. Just open PhpStorm (or whatever), edit away and it gets automatically uploaded..

    • Rajan Davis

      Used WinSCP on my Windows environment, it's waaaaaaaaaaay faster than the Windows version of Cyberduck and you don't have to worry about file permission issues (some files cannot be edited when using Cyberduck). I will check this out more over time, not a huge fan of developing on Windows, but this seems to make it a lot nicer (especially compared to Cyberduck and Adobe Dreamweaver).

      If you are developing on Mac or Linux and you like using terminal, I would recommend checking out the Cyberduck CLI. I have started building some bash scripts so that I can automate pushing my code into source control, minifying javascript, and reuploading files where they need to go. Using the Cyberduck CLI allows you to combine it with any other command line ecosystem like NPM, homebrew, apt, etc. so you have a lot of power at your fingertips.

    • Anuj Behl

      That's really interesting, Rajan.

      I have been using Windows for development all my life and after making a switch to Mac a few months ago, I couldn't figure out where to start. So, I ended up installing Windows virtually on Mac and continued with my previous tools laugh. Looks like spending some time learning Mac could be worth it. wink

      Totally agree on WinSCP yes

    • Bastiaan van der Kooij

      Oracle should consider making a nice donation to the free WinSCP, as without them it would be near impossible to edit CP in a productive manner on Windows (as I just learned :) )