All WebDAV clients fall into one of three categories—standalone applications, file-explorer extensions, or filesystem implementations. These categories broadly define the types of WebDAV functionality available to users. Table C.1, “Common WebDAV clients” gives our categorization as well as a quick description of some common pieces of WebDAV-enabled software. You can find more details about these software offerings, as well as their general category, in the sections that follow.
Table C.1. Common WebDAV clients
|Adobe Photoshop||Standalone WebDAV application||X||Image editing software, allowing direct opening from, and writing to, WebDAV URLs|
|cadaver||Standalone WebDAV application||X||X||Command-line WebDAV client supporting file transfer, tree, and locking operations|
|DAV Explorer||Standalone WebDAV application||X||X||X||Java GUI tool for exploring WebDAV shares|
|Adobe Dreamweaver||Standalone WebDAV application||X||Web production software able to directly read from and write to WebDAV URLs|
|Microsoft Office||Standalone WebDAV application||X||Office productivity suite with several components able to directly read from and write to WebDAV URLs|
|Microsoft Web Folders||File-explorer WebDAV extension||X||GUI file explorer program able to perform tree operations on a WebDAV share|
|GNOME Nautilus||File-explorer WebDAV extension||X||GUI file explorer able to perform tree operations on a WebDAV share|
|KDE Konqueror||File-explorer WebDAV extension||X||GUI file explorer able to perform tree operations on a WebDAV share|
|Mac OS X||WebDAV filesystem implementation||X||Operating system that has built-in support for mounting WebDAV shares.|
|Novell NetDrive||WebDAV filesystem implementation||X||Drive-mapping program for assigning Windows drive letters to a mounted remote WebDAV share|
|SRT WebDrive||WebDAV filesystem implementation||X||File transfer software, which, among other things, allows the assignment of Windows drive letters to a mounted remote WebDAV share|
|davfs2||WebDAV filesystem implementation||X||Linux filesystem driver that allows you to mount a WebDAV share|
A WebDAV application is a program that speaks WebDAV protocols with a WebDAV server. We'll cover some of the most popular programs with this kind of WebDAV support.
On Windows, several well-known applications contain integrated WebDAV client functionality, such as Microsoft's Office, Adobe's Photoshop and Dreamweaver programs. They're able to directly open and save to URLs, and tend to make heavy use of WebDAV locks when editing a file.
Note that while many of these programs also exist for Mac OS X, they do not appear to support WebDAV directly on that platform. In fact, on Mac OS X, thedialog box doesn't allow one to type a path or URL at all. It's likely that the WebDAV features were deliberately left out of Macintosh versions of these programs, since OS X already provides such excellent low-level filesystem support for WebDAV.
cadaver is a bare-bones Unix command-line program for browsing and changing WebDAV shares. It uses the neon HTTP library—not surprisingly, since both neon and cadaver are written by the same author. cadaver is free software (GPL license) and is available at http://www.webdav.org/cadaver/.
Using cadaver is similar to using a command-line FTP program, and thus it's extremely useful for basic WebDAV debugging. It can be used to upload or download files in a pinch, to examine properties, and to copy, move, lock, or unlock files:
$ cadaver http://host/repos dav:/repos/> ls Listing collection `/repos/': succeeded. Coll: > foobar 0 May 10 16:19 > playwright.el 2864 May 4 16:18 > proofbypoem.txt 1461 May 5 15:09 > westcoast.jpg 66737 May 5 15:09 dav:/repos/> put README Uploading README to `/repos/README': Progress: [=============================>] 100.0% of 357 bytes succeeded. dav:/repos/> get proofbypoem.txt Downloading `/repos/proofbypoem.txt' to proofbypoem.txt: Progress: [=============================>] 100.0% of 1461 bytes succeeded.
DAV Explorer is another standalone WebDAV client, written in Java. It's under a free Apache-like license and is available at http://www.ics.uci.edu/~webdav/. It does everything cadaver does, but has the advantages of being portable and being a more user-friendly GUI application. It's also one of the first clients to support the new WebDAV Access Control Protocol (RFC 3744).
Of course, DAV Explorer's ACL support is useless in this
case, since mod_dav_svn doesn't support
it. The fact that both cadaver and DAV Explorer support
some limited DeltaV commands isn't particularly useful
either, since they don't allow
requests. But it's not relevant anyway; we're assuming all
of these clients are operating against an autoversioning
Some popular file explorer GUI programs support WebDAV extensions that allow a user to browse a DAV share as though it was just another directory on the local computer, and to perform basic tree editing operations on the items in that share. For example, Windows Explorer is able to browse a WebDAV server as a “network place.” Users can drag files to and from the desktop, or can rename, copy, or delete files in the usual way. But because it's only a feature of the file explorer, the DAV share isn't visible to ordinary applications. All DAV interaction must happen through the explorer interface.
Microsoft was one of the original backers of the WebDAV specification, and first started shipping a client in Windows 98, which was known as Web Folders. This client was also shipped in Windows NT 4.0 and Windows 2000.
The original Web Folders client was an extension to Explorer, the main GUI program used to browse filesystems. It works well enough. In Windows 98, the feature might need to be explicitly installed if Web Folders aren't already visible inside My Computer. In Windows 2000, simply add a new “network place,” enter the URL, and the WebDAV share will pop up for browsing.
With the release of Windows XP, Microsoft started shipping
a new implementation of Web Folders, known as the WebDAV
Mini-Redirector. The new implementation is a
filesystem-level client, allowing WebDAV shares to be mounted
as drive letters. Unfortunately, this implementation is
incredibly buggy. The client usually tries to convert HTTP
http://host/repos) into UNC share
\\host\repos); it also often
tries to use Windows Domain authentication to respond to
basic-auth HTTP challenges, sending usernames as
HOST\username. These interoperability
problems are severe and are documented in numerous places around
the Web, to the frustration of many users. Even Greg Stein,
the original author of Apache's WebDAV module, bluntly
states that XP Web Folders simply can't operate against an Apache
Windows Vista's initial implementation of Web Folders seems to be almost the same as XP's, so it has the same sort of problems. With luck, Microsoft will remedy these issues in a Vista Service Pack.
However, there seem to be workarounds for both XP and Vista that allow Web Folders to work against Apache. Users have mostly reported success with these techniques, so we'll relay them here.
On Windows XP, you have two options. First, search
Microsoft's web site for update KB907306, “Software
Update for Web Folders.” This may fix all your
problems. If it doesn't, it seems that the original pre-XP
Web Folders implementation is still buried within the
system. You can unearth it by going to Network
Places and adding a new network place. When prompted,
enter the URL of the repository, but include a
port number in the URL. For
example, you should enter
Respond to any authentication prompts with your Subversion
On Windows Vista, the same KB907306 update may clear
everything up. But there may still be other issues. Some
users have reported that Vista considers
http:// connections insecure, and thus
will always fail any authentication challenges from Apache
unless the connection happens
https://. If you're unable to connect
to the Subversion repository via SSL, you can tweak the
system registry to turn off this behavior. Just change the
value of the
2. A final warning: be sure to set up the Web
Folders to point to the repository's root directory
/), rather than some subdirectory
/trunk. Vista Web Folders
seems to work only against repository roots.
In general, while these workarounds may function for you, you might get a better overall experience using a third-party WebDAV client such as WebDrive or NetDrive.
Nautilus is the official file manager/browser for the GNOME desktop (http://www.gnome.org), and Konqueror is the manager/browser for the KDE desktop (http://www.kde.org). Both of these applications have an explorer-level WebDAV client built in, and they operate just fine against an autoversioning repository.
In GNOME's Nautilus, select themenu item and enter the URL in the dialog box presented. The repository should then be displayed like any other filesystem.
In KDE's Konqueror, you need to use the
webdav:// scheme when entering the URL in
the location bar. If you enter
http:// URL, Konqueror will behave
like an ordinary web browser. You'll likely see the generic
HTML directory listing produced
by mod_dav_svn. When you enter
webdav://host/repos instead of
http://host/repos, Konqueror becomes a
WebDAV client and displays the repository as a
The WebDAV filesystem implementation is arguably the best sort of WebDAV client. It's implemented as a low-level filesystem module, typically within the operating system's kernel. This means that the DAV share is mounted like any other network filesystem, similar to mounting an NFS share on Unix or attaching an SMB share as a drive letter in Windows. As a result, this sort of client provides completely transparent read/write WebDAV access to all programs. Applications aren't even aware that WebDAV requests are happening.
Both WebDrive and NetDrive are excellent commercial products that allow a WebDAV share to be attached as drive letters in Windows. As a result, you can operate on the contents of these WebDAV-backed pseudodrives as easily as you can against real local hard drives, and in the same ways. You can purchase WebDrive from South River Technologies (http://www.southrivertech.com). Novell's NetDrive is freely available online, but requires users to have a NetWare license.
Apple's OS X operating system has an integrated
filesystem-level WebDAV client. From the Finder, select the
webdav filesystem type with the
$ mount -t webdav http://svn.example.com/repos/project /some/mountpoint $
Note that if your mod_dav_svn is older than version 1.2, OS X will refuse to mount the share as read/write; it will appear as read-only. This is because OS X insists on locking support for read/write shares, and the ability to lock files first appeared in Subversion 1.2.
Also, OS X's WebDAV client can sometimes be overly
sensitive to HTTP redirects. If OS X is unable to mount the
repository at all, you may need to enable
BrowserMatch directive in the Apache
BrowserMatch "^WebDAVFS/1." redirect-carefully
Linux davfs2 is a filesystem module for the Linux kernel, whose development is organized at http://savannah.nongnu.org/projects/davfs2. Once you install davfs2, you can mount a WebDAV network share using the usual Linux mount command:
$ mount.davfs http://host/repos /mnt/dav
 WebDAV support was removed from Microsoft Access for some reason, but it exists in the rest of the Office suite.