WebDAV

From Wikipedia, the free encyclopedia - View original article

WebDAV
Port(s)80, 443
RFC(s)RFC 2518, RFC 4918
OSI layerApplication
 
  (Redirected from Webdav)
Jump to: navigation, search
WebDAV
Port(s)80, 443
RFC(s)RFC 2518, RFC 4918
OSI layerApplication

Web Distributed Authoring and Versioning (WebDAV) is an extension of the Hypertext Transfer Protocol (HTTP) that facilitates collaboration between users in editing and managing documents and files stored on World Wide Web servers. A working group of the Internet Engineering Task Force (IETF) defined WebDAV in RFC 4918.

The WebDAV protocol makes the Web a readable and writable medium.[1] It provides a framework for users to create, change and move documents on a server; typically a web server or web share. The most important features of the WebDAV protocol include the maintenance of properties about an author or modification date, namespace management, collections, and overwrite protection. Maintenance of properties includes such things as the creation, removal, and querying of file information. Namespace management deals with the ability to copy and move web pages within a server’s namespace. Collections deal with the creation, removal, and listing of various resources. Lastly, overwrite protection handles aspects related to locking of files.

The WebDAV working group concluded its work in March 2007, after the Internet Engineering Steering Group (IESG) accepted an incremental update to RFC 2518. Other extensions left unfinished at that time, such as the BIND method, have been finished by their individual authors, independent of the formal working group.

As of 2013, many modern operating systems provide built-in client-side support for WebDAV.

History[edit]

WebDAV1 began in 1996 when Jim Whitehead, a PhD graduate from UC Irvine, worked with the World Wide Web Consortium (W3C) to host two meetings to discuss the problem of distributed authoring on the World Wide Web with interested people.[2][3] Tim Berners-Lee's original vision of the Web was that of a medium for both reading and writing. In fact, Berners-Lee's first web browser, called WorldWideWeb, was able to both view and edit web pages; but, as the Web grew, it became a read-only medium for most users. Whitehead and other like-minded people wanted to fix that limitation.[4]

The W3C meeting decided to form an IETF working group, because the new effort would lead to extensions to HTTP, which was being standardized at the IETF.

As work began on the protocol, it became clear that handling both distributed authoring and versioning would involve too much work and that the tasks would have to be separated. The WebDAV group focused on distributed authoring, and left versioning for the future. Versioning was added later by the Delta-V extension — see the Extensions section below.

The protocol consists of a set of new methods and headers for use in HTTP. The added methods include:

Implementations[edit]

Servers[edit]

Clients[edit]

Linux users can mount WebDAV shares using the davfs2 and the fusedav file system modules which mount them as Coda or FUSE filesystems. KDE has native WebDAV support as part of kio_http.[5] This enables the file managers Dolphin & Konqueror,[6] and every other KDE application to interact directly with WebDAV servers. All applications using the GIO library, including the Nautilus file manager, have access to WebDAV through GNOME Virtual File System (GVFS). Many Linux distributions also include the cadaver command-line client interface,[7] which provides an FTP-like command set.

Mac OS X version 10.0 and following support WebDAV shares natively as a type of filesystem. The system can mount WebDAV-enabled server directories to the filesystem using the traditional BSD mounting mechanism or through the "Connect to Server" dialog found in the Finder. Mac OS X version 10.1.1 introduced support for HTTP Digest Access authentication. Mac OS X 10.4 (Tiger) extended WebDAV interoperability to include support for the HTTPS scheme, proxies, and additional methods of authentication.[8] The Finder presents a WebDAV share as an external disk, allowing users to interact with WebDAV just as they would with any other filesystem. Apple's iDisk, part of its former MobileMe service, used WebDAV for file access.[9]

Microsoft introduced WebDAV client support in Microsoft Windows 98 with a feature called "Web folders". This client consisted of an OLE object which could be accessed by any OLE software, and was installed as an extension to Windows Explorer (the desktop/file manager) and was later included in Windows 2000. In Windows XP, Microsoft added the Web Client service also known as the WebDAV mini-redirector[10] which is preferred by default over the old Web folders client. This newer client works as a system service at the network-redirector level (immediately above the file-system), allowing WebDAV shares to be assigned to a drive letter and used by any software. The redirector also allows WebDAV shares to be addressed via UNC paths (e.g. http://host/path/ is converted to \\host\path\) for compatibility with Windows filesystem APIs. Some versions of the redirector are reported to have some limitations in authentication support.[11] In addition, WebDAV over HTTPS works only if a computer has KB892211-version files or newer installed. Otherwise Windows displays "The folder you entered does not appear to be valid. Please choose another" when adding a network resource. NOTE: 892211 has been superseded by KB907306. Windows Vista includes only the WebDAV redirector, but if you install a version of Office, Internet Explorer, OLE-DB or "Microsoft Update for Web Folders" you will get the original "Web folders" client. The update will only work on the 32-bit version of XP/Vista.[12] Microsoft states that 64 bit versions of Windows will never support the "Web folders" client. Instead users are limited to using WebDAV via the native Web Client service redirector.[13]

Alternatives to WebDAV[edit]

Documents produced by the working group[edit]

The WebDAV working group produced several works:

Other documents published through IETF[edit]

Extensions and derivatives[edit]

For versioning, the Delta-V protocol under the Web Versioning and Configuration Management working group adds resource revision tracking, published in RFC 3253.

For searching and locating, the DAV Searching and Locating (DASL) working group never produced any official standard although there are a number of implementations of its last draft. Work continued as non-working-group activity.[14] The WebDAV Search specification attempts to pick up where the working group left off, and was published as RFC 5323 in November 2008.[15]

For calendaring, CalDAV is a protocol allowing calendar access via WebDAV. CalDAV models calendar events as HTTP resources in iCalendar format, and models calendars containing events as WebDAV collections.

For groupware, GroupDAV is a variant of WebDAV which allows client/server groupware systems to store and fetch objects such as calendar items and address book entries instead of web pages.

For MS Exchange interoperability, WebDAV can be used for reading/updating/deleting items in a mailbox or public folder. WebDAV for Exchange has been extended by Microsoft to accommodate working with messaging data. Exchange Server version 2000, 2003, and 2007 support WebDAV. However, WebDAV support has been discontinued in Exchange 2010 [16] in favor of Exchange Web Services (EWS), a SOAP/XML based API.

Additional Windows-specific extensions[edit]

As part of the Windows Server Protocols (WSPP) documentation set,[17] Microsoft published the following protocol documents detailing extensions to WebDAV:

See also[edit]

References[edit]

External links[edit]