Customer Portal

Get Involved. Join the Conversation.


    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 
    18970 Views, 24 Comments
    Overview of your WebDAV options by OS/Vendor

    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


    • Christopher Tarabochia

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

    • david fulton

      Hi everyone,

      Please note that the attached document has been updated with more specific information on Vista and Windows 7 support (through native OS connections). We are at the point of strongly recommending the WebDrive offering ( as the only viable option for windows users. 

    • Evelyn Yoder

      This new Developer Documentation is great - just what we needed.

    • Christopher Tarabochia

      The above document has been updated to provide a new recommended option for Mac OS X users. Also, we have made the format of the document more universal and it is now a PDF.

    • Leif Wickland

      Our new recommendation for Mac OS X users is to use Cyberduck, a free WebDAV client, instead of the built-in client.  Beginning around version 10.5, Mac OS X began sending many times more WebDAV requests to accomplish the same action.  Cyberduck is much more efficient in the requests it sends, so you'll have a much more responsive experience when interacting with WebDAV.

    • Evelyn Yoder

      We have a VHOST-based hosted site. (which is apparently different from a hosted site...)

      Anyway, Windows 7 doesn't play well with WebDAV, but this is what worked for us: 

      • Download and install WebDrive
      • Use this format for the site address/URL: <>

      The formats recommended in do not work.

    • Dan Stevens

      An alternative to WebDrive for Windows users is BitKinex. It works well although it doesn't offer drive letter mounting that WebDrive does. I am able to download an entire site's euf files without problems. It is freeware unlike WebDrive, which has a trail period.

    • Tim M


      The following worked for me on Windows 7 and it looks like it works.


      On Windows 7 try the following:


      1)     Click Start and click Computer.
      2)     Click Map network drive.
      3)     Click the link “Connect to a Web site that you can use to store your documents and pictures”, then click next
      4)     Click Choose a custom network location
      5)     Enter your WebDAV URL
      6)     Click next
      7)     Enter your user name and password when prompted.


      Only the secure connection appears to work with https:// on the 443 port with Windows 7.


    • Mpepper

       We have updated answer 2600 with the correct information on Vista and XP. 

      The correct address is  https://<interfacename>  you do not have to specify the port.

      Meg Pepper



    • Ken Golubski

      I can connect and view the files with BitKinex, but when we try to update a file, on the upload, all we get it:


      X-WebDAV-Status: 403 Forbidden


      I assume this is a permissions issue. Where is that set up at ?




    • Ernie Turner

      What file are you attempted to update?

    • Ken Golubski

      All my bad. I was in the wrong folder. Cry


      Thanks for the reply !!



    • Steven Hughes

      It would be great if you re-thought this WebDAV decision.  WebDAV connectivity using BitKinex is hit or miss, and using Dreamweaver... it takes hours for me to do a 'get' request from the server, which also holds hostage my ability to do anything else in Dreamweaver while waiting for the 'get' command to finish.  I manage 10+ sites (with 5 languages each) so much of my day is wasted watching files sync. 

      FTP would be better for about a million reasons but here's my top 5...

      1.) I could have my file transfers working in the background (using filezilla or another app) while I do the work I need to do using dreamweaver.

      2.) What benefit does transferring over http really have? (ssh...yawn...)

      3.) SFTP is also secure.

      4.) I've worked for several fortune 100 companies, none of the ones I worked for (except my current one) require a webDAV environment.

      5.) WebDAV is PC friendly, mac... not so much.

    • david fulton

      Hi Steven,

      We've updated our recommendations on WebDAV clients. BitKinex as you stated is a little hit and miss. We continue to discuss File Transfer on a regular basis here at Oracle RightNow and wouldn't rule out alternatives in the future, but for the time being, CyberDuck would be our recommendation as a great tool to use with our solution.

    • Rajan Davis

      Just a heads up, if you want to use CyberDuck as a webdav solution, you have to use version 4.4.3 (can only confirm that this for Mac). Apparently there is resolved in 4.5; however, the latest version is 4.6.3 and I could not get CyberDuck to upload files on both the Mac and Windows operating systems. I kept getting an internal server error as well as an error regarding the file attributes.