WebDAV — a Hybrid Approach to File Access over HTTP

Introduction

In previous articles, we covered both classic protocols (FTP, SFTP, SMB) and the modern object storage standard S3. However, there’s another protocol that combines features of traditional file access with HTTP — WebDAV.

This protocol became popular thanks to its simplicity, universality, and ability to work with files as if they were on a local disk, but over the internet.

What is WebDAV?

WebDAV (Web Distributed Authoring and Versioning) is an extension of the HTTP protocol, developed in the late 1990s.

It allows users not only to download and upload files but also to manage them (create, move, delete, edit). WebDAV adds to HTTP the ability to work with folders, file locking, and versioning.

Unlike S3, which uses a flat object structure, WebDAV preserves the familiar hierarchy of folders and files, making it more intuitive.

How does WebDAV work?

WebDAV extends standard HTTP by adding new methods:

• PROPFIND — retrieve metadata about files and folders.
• MKCOL — create a new folder (collection).
• COPY / MOVE — copy or move files.
• LOCK / UNLOCK — lock files to prevent simultaneous editing.
• PUT / GET — upload and download files.
• DELETE — remove files and folders.

⚡ Works over standard 80/443 ports, which is convenient in restricted networks. Authentication: Basic/Digest, and in modern implementations — OAuth or other mechanisms.

Advantages of WebDAV

• Easy integration: simple to set up on web servers (Apache, Nginx, IIS) and in cloud services (Nextcloud, ownCloud, Yandex.Disk).
• Intuitive: familiar folder hierarchy, similar to SMB.
• Cross-platform: supported in Windows, macOS, Linux, and popular applications (MS Office, Photoshop).
• Flexibility: file locking and collaboration support.
• Security: HTTPS + various authentication methods.

Disadvantages of WebDAV

• Limited scalability: not designed for billions of objects like S3.
• Performance: may be slower with large files or deep hierarchies.
• Metadata: supported only at a basic level, less flexible than in S3.
• Implementation-dependent: quality varies greatly depending on the server side.

Where is WebDAV used?

• Collaborative document editing (Nextcloud, ownCloud, CMS).
• File synchronization (e.g., integration with Dropbox/Google Drive).
• Web content editing (historically — publishing pages directly to the server).
• OS integration: mounting remote folders as network drives.
• Backups: automated cloud backups.

WebDAV vs. S3: which to choose?

• Choose WebDAV if you need a familiar file structure, OS integration, or collaborative document editing.
• Choose S3 if you’re dealing with massive amounts of data, require scalability, and need an API for applications.

Conclusion

WebDAV is a bridge between traditional file protocols and cloud technologies. It combines the simplicity of file handling (like SMB or FTP) with the universality of HTTP.

While it’s not as scalable as S3, its flexibility and OS support make it an excellent choice for many scenarios — from personal use to enterprise solutions.

Resources

• RFC 4918 — HTTP Extensions for WebDAV
• Nextcloud Docs
• Apache mod_dav Documentation