How Many Cryptocurrencies Are There? A Look at the Proliferation of Digital Currencies


In the early days of the World Wide Web, the HTTP protocol was designed primarily for serving up static HTML documents. But as the web evolved, the need for a protocol that could support collaborative authoring and file management became increasingly apparent. Enter WebDAV.

WebDAV, which stands for "Web Distributed Authoring and Versioning," is an extension of the HTTP protocol that adds features for collaborative content authoring and management. Essentially, it turns a web server into a file server, allowing users to create, move, copy, and delete files and folders just like they would on a local machine.

In this comprehensive guide, we‘ll dive deep into the WebDAV protocol. We‘ll explore its origins, break down its key features, compare it to alternative protocols, and look at how it‘s being used in practice today. Along the way, we‘ll incorporate insights from industry experts and relevant data to paint a complete picture of this important web standard.

The Origins of WebDAV

To understand WebDAV, we first need to understand a bit about the history of HTTP. HTTP, or Hypertext Transfer Protocol, is the foundation of data communication for the World Wide Web. Developed by Tim Berners-Lee in the early 1990s, HTTP is a stateless protocol that defines how messages are formatted and transmitted between servers and clients.

The original version of HTTP (0.9) was extremely simple. It only supported one command (GET) and did not include headers or error codes. Over time, new versions of HTTP added support for additional methods like POST, HEAD, and OPTIONS, as well as headers, status codes, and security features.

However, HTTP was still primarily designed for serving up read-only content. There was no standard way to create, edit, or manage files on a web server. This began to change in the mid-1990s with the rise of dynamic websites and web applications. Suddenly, there was a need for a protocol that could support collaborative authoring over the web.

In 1996, Jim Whitehead, a researcher at UC Irvine, posted a proposal to the www-talk mailing list titled "World-Wide Web Distributed Authoring and Versioning (WebDAV)." The proposal outlined a set of extensions to HTTP that would support remote collaborative authoring.

The WebDAV working group was formed shortly thereafter under the auspices of the Internet Engineering Task Force (IETF). The group, which included representatives from Microsoft, Netscape, IBM, and other major tech companies, worked to refine the WebDAV specification.

In 1999, RFC 2518 was published, defining the WebDAV protocol. Subsequent RFCs have added extensions and improvements to the protocol, but the core has remained largely the same.

Understanding the WebDAV Protocol

At its core, WebDAV is a set of new methods and headers for HTTP that allow users to collaboratively author and manage files on remote web servers.

Some of the key methods introduced by WebDAV include:

  • PUT: Uploads a representation of the specified resource.
  • DELETE: Deletes the specified resource.
  • MKCOL: Creates a new collection (i.e., a directory).
  • COPY: Creates a duplicate of the source resource at the specified destination.
  • MOVE: Moves the source resource to the specified destination.
  • LOCK: Puts a lock on the specified resource.
  • UNLOCK: Removes a lock from the specified resource.

In addition to these methods, WebDAV introduces the concept of "collections." In WebDAV, a collection is a resource that can contain other resources, similar to a directory in a file system. Collections can be nested, creating a hierarchical structure.

WebDAV also introduces "properties," which are metadata associated with a resource. Properties can include things like the author of a document, the creation date, keywords, etc. Properties are stored as XML and can be retrieved and set using the PROPFIND and PROPPATCH methods, respectively.

Key Features of WebDAV

Now that we have a basic understanding of how WebDAV works, let‘s dive deeper into some of its key features.


One of the most important features of WebDAV is support for locking. Locking allows a user to temporarily prevent others from modifying a resource while they are working on it. This is crucial for preventing conflicts when multiple users are collaborating on the same document.

WebDAV supports two types of locks: exclusive locks and shared locks. An exclusive lock gives a single user exclusive write access to a resource. A shared lock allows multiple users to read a resource, but prevents anyone from writing to it.

Locks in WebDAV are "advisory," meaning it‘s up to the client to respect the lock. A rogue client could choose to ignore a lock, but most WebDAV clients will respect locks by default.


Another key feature of WebDAV is versioning. Versioning allows you to track changes to a resource over time and revert to previous versions if needed.

WebDAV versioning works by storing multiple versions of a resource, each with a unique version name. Clients can retrieve a specific version of a resource by including the version name in the URL.

WebDAV also supports "auto-versioning," where the server automatically creates a new version of a resource every time it‘s modified. This provides a complete audit trail of all changes made to a resource.

Access Control

WebDAV includes support for access control, allowing server administrators to specify who can read, write, or modify resources. Access control in WebDAV is based on the concept of "principals," which can be individual users or groups.

WebDAV uses the HTTP methods ACL and REPORT to manage access control lists (ACLs) and retrieve information about principals, respectively.

Namespace Management

Finally, WebDAV provides support for namespace management, allowing clients to copy and move resources within a server‘s namespace.

The COPY method is used to create a duplicate of a resource, while the MOVE method is used to relocate a resource. These methods work on both individual resources and entire collections.

WebDAV vs. Alternative Protocols

WebDAV is not the only protocol that supports remote file access and collaboration. Let‘s see how it stacks up against some of the alternatives.

FTP (File Transfer Protocol)

FTP is one of the oldest protocols for transferring files over the internet. While it can be used for some of the same purposes as WebDAV, it has several disadvantages:

  • FTP is not secure. Passwords and data are transmitted in plain text.
  • FTP does not support encryption.
  • FTP does not provide locking or versioning features.

SFTP (SSH File Transfer Protocol)

SFTP is a secure version of FTP that runs over SSH. While it provides encryption and authentication, it still lacks many of the collaboration features of WebDAV like locking and versioning.

SMB/CIFS (Server Message Block/Common Internet File System)

SMB and CIFS are protocols used primarily for file sharing on local networks. While they support features like locking and access control, they are not well-suited for use over the internet due to security concerns and issues with firewalls and NAT traversal.

WebDAV in Practice

So how widely used is WebDAV today? Let‘s look at some data.

According to W3Techs, a web technology survey service, WebDAV is used by 2.1% of all websites. While this may seem like a small percentage, it still represents over 11 million websites.

WebDAV usage is particularly common in certain industries and use cases. For example, many content management systems (CMS) use WebDAV to enable remote authoring and collaboration. WordPress, the world‘s most popular CMS, has supported WebDAV since version 2.1.

Cloud storage providers also commonly support WebDAV. Box, a popular enterprise cloud storage service, uses WebDAV as one of its primary APIs for file access and synchronization. According to Box, over 69% of the Fortune 500 use their service, indirectly relying on WebDAV.

Beyond its use in web-based applications, WebDAV is also supported by many desktop software applications. Microsoft Office, for example, has native support for opening and saving files to WebDAV servers. This allows users to collaborate on Office documents directly from within the application.

The Future of WebDAV

While WebDAV has been around for over two decades, it‘s far from a static protocol. The WebDAV community continues to work on extensions and improvements to the standard.

One area of active development is WebDAV notifications. The WebDAV Notifications Extension (RFC 5423) defines a way for servers to send notifications to clients when resources are created, modified, or deleted. This allows for real-time synchronization and collaboration.

Another area of development is integration with other web standards. For example, there have been proposals to integrate WebDAV with the Linked Data Platform (LDP) to enable WebDAV resources to be part of the Semantic Web.

As the web continues to evolve, it‘s likely that WebDAV will evolve with it, finding new applications and use cases.


WebDAV is a powerful protocol that extends the functionality of HTTP to support collaborative authoring and file management. With features like locking, versioning, and access control, it provides a robust platform for building web-based collaboration tools.

While it may not be as widely known as protocols like FTP or HTTP itself, WebDAV is a critical part of the web infrastructure, powering everything from content management systems to cloud storage platforms.

As we‘ve seen in this guide, WebDAV has a rich history and a vibrant community that continues to push the protocol forward. With ongoing development and integration with other web standards, it‘s likely that WebDAV will continue to play an important role in the web ecosystem for years to come.

Whether you‘re a web developer looking to add collaboration features to your application, or simply a user looking to understand how your cloud storage service works under the hood, understanding WebDAV is key to navigating the modern web.