WebDAV client library for Rust
This library is composed of 3 feature-gated layers:
- Low-level I/O-free coroutines: no_std-compatible state machines containing the whole WebDAV logic, usable anywhere
- Mid-level light client: a standard, blocking client wrapping a stream you opened yourself
- High-level full client: the light client plus TCP connections and TLS negotiations handled for you
- CalDAV: calendar collections and calendar object resources, with discovery of the calendar home set.
- CardDAV: address book collections and contact cards, with discovery of the address book home set.
- Discovery: current-user-principal lookup and home-set resolution, surfacing redirects to the caller instead of following them.
- Incremental sync: collection synchronization with sync tokens, batch multiget and ETag-only enumeration for change detection.
- Authentication: HTTP Basic and Bearer.
- Full standard, blocking client with TLS support:
- Rustls with ring crypto (requires
rustls-ringfeature, enabled by default) - Rustls with aws crypto (requires
rustls-awsfeature) - Native TLS (requires
native-tlsfeature)
- Rustls with ring crypto (requires
Tip
I/O WebDAV is written in Rust and uses cargo features to gate the client layers. The default feature set is declared in Cargo.toml or on docs.rs.
| RFC | What is covered |
|---|---|
| 4918 | WebDAV core: property discovery and patching, collection creation, copy, move, delete, get, put, options, report and multistatus parsing |
| 4791 | CalDAV: calendar collections and calendar object resources, with calendar home-set discovery |
| 5397 | WebDAV current principal: current-user-principal discovery |
| 6352 | CardDAV: address book collections and contact cards, with address book home-set discovery, batch multiget and ETag-only enumeration |
| 6578 | Collection synchronization: sync-collection report and sync tokens |
The whole API is documented on docs.rs, including runnable snippets for every coroutine and client.
Complete runnable programs live in ./examples; the tests also demonstrate real usage against live CalDAV and CardDAV servers.
This project is developed with AI assistance. This section documents how, so users and downstream packagers can make informed decisions.
- Tools: Claude Code (Anthropic), invoked locally with a persistent project-scoped memory and a small set of repo-specific rules.
- Used for: Refactors, mechanical multi-file edits, boilerplate (feature gates, error enums, derive macros, trait impls), test scaffolding, doc polish, exploratory design conversations.
- Not used for: Engineering, critical code, git manipulation (commit, merge, rebase…), real-world tests.
- Verification: Every AI-assisted change is read, compiled, tested, and formatted before commit. Behavioural correctness is verified against the relevant RFC or upstream spec, not assumed from the model output. Tests are never adjusted to fit AI-generated code; the code is adjusted to fit correct behaviour.
- Limitations: AI models occasionally produce code that compiles and passes tests but is subtly wrong. The verification workflow catches most of this; it does not catch all of it. Bug reports are welcome and taken seriously.
- Last reviewed: 16/07/2026
This project is licensed under either of:
at your option.
- Chat on Matrix
- News on Mastodon or RSS
- Mail at pimalaya.org@posteo.net
Contributions are welcome: start with CONTRIBUTING.md, which opens with the Pimalaya-wide guides to read first.
Special thanks to the NLnet foundation and the European Commission that have been financially supporting the project for years:
- 2022 → 2023: NGI Assure
- 2023 → 2024: NGI Zero Entrust
- 2024 → 2026: NGI Zero Core
- 2027 in preparation…
If you appreciate the project, feel free to donate using one of the following providers:
