hacdias /webdav

A simple and standalone WebDAV server.

★ 5,989⑂ 571👁 33⑃ 192● 185▤ 75
GoMITCreated 2017-08-03
Download: v5.17.3v5.17.3 ↓5.17.32026-10-30
+2
Daily
5,989
stars
571
forks
33
watchers
192
prs
185
issues
75
releases

README

webdav






A simple and standalone WebDAV server.

 Install

For a manual install, please refer to the releases page and download the correct binary for your system. Alternatively, you can build or install it from source using the Go toolchain. You can either clone the repository and execute go build, or directly install it, using:


go install github.com/hacdias/webdav/v5@latest


 Homebrew

If you have Homebrew available on your system, you can also install webdav using it: 


brew install webdav


 Docker

Docker images are provided on both GitHub's registry and Docker Hub. You can pull the images using one of the following two commands. Note that this commands pull the latest released version. You can use specific tags to pin specific versions, or use main for the development branch.

bash
 GitHub Registry
docker pull ghcr.io/hacdias/webdav:latest

 Docker Hub
docker pull hacdias/webdav:latest


 Usage

For usage information regarding the CLI, run webdav --help.

 Container

To run the container, you can refer to the compose.yml file which provides a minimal setup. Additionally, you also need to create a configuration file, as explained below.

The equivalent Docker command to the aforementioned compose file would be as follows:

bash
docker run \
  -p 6065:6065 \
  -v ./config.yml:/config.yml:ro \
  -v ./data:/data \
  ghcr.io/hacdias/webdav -c /config.yml


If you are using fail2ban, it would be helpful to add the parameters listed below. They will assist in analyzing 
the log.

bash
--log-driver journald \
--name webdav \


 Partial updates

This server supports partial file updates compatible with SabreDAV's PATCH extension. This is not an official WebDAV specification. Requests must use the application/x-sabredav-partialupdate content type, include Content-Length, and provide the target range in X-Update-Range.

Supported X-Update-Range values are:

- bytes=start-end
- bytes=start-
- bytes=-N
- append

For clients that use it, the server also supports partial PUT requests with Content-Range, for example Content-Range: bytes 6-8/. This is an extra compatibility path and should be treated as a client/server agreement.

 Configuration

The configuration can be provided as a YAML, JSON or TOML file. Below is an example of a YAML configuration file with 
all the options available, as well as what they mean. Top-level keys use camelCase and keys nested inside a section use snake_case.

yaml
address: 0.0.0.0
port: 6065

 TLS-related settings if you want to enable TLS directly.
tls: false
cert: cert.pem
key: key.pem

 Send a Strict-Transport-Security header on HTTPS responses, so browsers only
 use HTTPS with this host. Set to true for 'max-age=31536000' (a year), or to
 the header value, such as 'max-age=31536000; includeSubDomains'. Only applies
 when this server handles TLS itself: behind a proxy, set the header there.
 Default is 'false'.
hsts: false

 Prefix to apply to the WebDAV path-ing. Default is '/'.
prefix: /

 Enable or disable de

Top issues

Latest release

v5.17.3 v5.17.3 2026-10-30
Changelog
 614d97526481d6ea048eb977e91ea7c9d64140cb feat: add configurable HSTS
 5ee1ba4a933346b4bbbe0719108472af6fb9ffee fix: map Windows lock roots back to request paths
 d08e2277baf9d4e287d7aa8078ee4c094dca5326 docs: update badges
 778116bfee49b5f38fc714112ede4743296aaa3b refactor: drop unreachable directory mount types
 34923d5057c7618ab06082015db386da6d5f0fbb docs: note that CORS credentials need specific origins
 91a45ed4ede16bb8e1e6216f8a16a7f95c086ab6 fix: reject malformed bcrypt hashes at startup
 d6ad0d82a0c5a47639fc0f5b21bb1ca8fc4e7b21 fix: report a refreshed lock's root as a reques

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON