hacdias/webdav

A simple and standalone WebDAV server.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 50 minutes ago
Added to GitGenius on September 11th, 2026
Created on August 3rd, 2017
Open Issues & Pull Requests: 18 (+0)
GitHub issues: Enabled
Number of forks: 554
Total Stargazers: 5,846 (+0)
Total Subscribers: 33 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.6 days
Mean response time: 36.9 days
90th percentile: 81.6 days
Tracked items: 73

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 10% of issues opened in the past year have been closed. Three people close 84% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 13
New in 7 days: 1
Closed in 7 days: 4
Avg open age: 802 days
Stale 30+ days: 11
Stale 90+ days: 11

Recent activity

Opened in 7 days: 1
Closed in 7 days: 4
Comments in 7 days: 1
Events in 7 days: 3

Top labels

  • help wanted (15)
  • enhancement (13)
  • bug (6)
  • upstream (1)

Most active issues this week

Detailed Description

webdav is a standalone WebDAV server written in Go that provides simple file access over the WebDAV protocol.

The tool solves the problem of needing a lightweight, self-contained WebDAV server for exposing filesystem resources over HTTP. It works by implementing the WebDAV protocol to allow clients to read, write, and manage files on a server through standard WebDAV operations. The server supports partial file updates compatible with SabreDAV's PATCH extension, accepting requests with the application/x-sabredav-partialupdate content type and range specifications, as well as partial PUT requests using Content-Range headers for client compatibility.

The project suits developers and operators who need a minimal WebDAV deployment without heavy dependencies. It works well for scenarios requiring straightforward file sharing or remote filesystem access. Installation is flexible: binaries are available for multiple systems, it can be built from source using the Go toolchain, installed via Homebrew, or run as a Docker container with provided compose configuration. Access control is managed through a configuration file supporting YAML, JSON, or TOML formats, with rules that can be specified as path prefixes or regex patterns. Rules are matched against resolved request paths and apply to all paths an operation touches, affecting collection listings, copy operations, and move or delete requests.

The project receives issue and pull request responses within one to two weeks. Work in the issue tracker centers on enhancements, bug fixes, and upstream-related items.