Weave Code
Sabredav Bundle Laravel Package
secotrust/sabredav-bundle
A Symfony bundle that integrates SabreDAV to add WebDAV, CalDAV, and CardDAV server capabilities to your application. It wires SabreDAV into Symfony’s configuration and services so you can expose calendars, contacts, and files with less boilerplate.
This bundle integrates the SabreDAV library into Symfony2
Frequently asked questions about Sabredav Bundle
- Is secotrust/sabredav-bundle compatible with Laravel?
- No. It is a Symfony2 bundle, not a Laravel package, and it wires SabreDAV into Symfony's dependency injection container, configuration, and event dispatcher. Laravel's container, routing, middleware, and config conventions are different, so adopting it as-is would mean importing Symfony2 abstractions into a Laravel app. Use sabre/dav directly and build a thin Laravel service provider instead.
- Can I install secotrust/sabredav-bundle in a Laravel app with Composer?
- You can try, but it will likely create dependency conflicts. Symfony2 reached end-of-life in 2019, and the bundle's Composer constraints probably conflict with modern Laravel on PHP 8.1 or newer and with current sabre/dav releases. Do not force-install it in a Laravel application; if you must audit it, use a disposable Composer project to inspect pinned versions and known CVEs.
- What Laravel versions does secotrust/sabredav-bundle support?
- None officially. The package targets Symfony2, not Laravel, and has no Laravel service provider, facade, or configuration integration. For Laravel 10 or 11 on PHP 8.2 and newer, use current sabre/dav 4.x with your own Laravel-native wiring.
- How do I add WebDAV, CalDAV, or CardDAV to a Laravel application?
- Use sabre/dav directly and create a Laravel service provider, a publishable config file, an explicit route group for the DAV endpoint, and auth middleware. Treat secotrust/sabredav-bundle as a design reference for configuration semantics such as server setup, plugin ordering, auth backend, principal backend, and tree nodes. Replace Symfony DI with Laravel container bindings and Symfony listeners with Laravel events or direct SabreDAV callbacks.
- Does secotrust/sabredav-bundle support PHP 8.2?
- It is unlikely to support PHP 8.2 because it is a frozen Symfony2 artifact with old dependency constraints. Check which sabre/dav major version the bundle pins and whether that version supports PHP 8.2 or newer in an isolated Composer project. The realistic modern stack is sabre/dav 4.x on PHP 8.2 with a Laravel integration layer.
- What authentication methods does secotrust/sabredav-bundle support for WebDAV?
- The bundle wires SabreDAV authentication backends into Symfony services, so the available methods depend on the SabreDAV auth plugin and backend you configure, such as HTTP Basic or a custom backend. It does not provide a Laravel auth middleware or token, OAuth, or SSO integration out of the box. In Laravel, implement the auth model you need in middleware and pass the resolved principal to SabreDAV's auth plugin.
- Can I use secotrust/sabredav-bundle for CalDAV and CardDAV in Laravel?
- The bundle demonstrates CalDAV and CardDAV wiring for Symfony2, but that wiring is not reusable in Laravel. Use sabre/dav's CalDAV and CardDAV plugins directly in your Laravel integration, and only add them if calendar or contact support is actually in scope. Plain WebDAV needs a smaller plugin set than CalDAV or CardDAV with principal discovery.
- What storage backends does secotrust/sabredav-bundle support?
- The bundle's storage support comes from SabreDAV, which can use filesystem, PDO, or custom tree implementations, and the bundle wires those into Symfony services. For Laravel, choose filesystem, PDO, S3, or a custom tree and bind it in your service provider. If you need multi-tenancy or per-user ACL enforcement, that logic must be implemented in your Laravel integration.
- Is secotrust/sabredav-bundle maintained and safe for production?
- Treat it as unmaintained. It is a Symfony2 bundle with 13 stars and 0 dependents, near-zero ecosystem validation, and an end-of-life Symfony2 dependency chain. Technical risk is high: old SabreDAV APIs, PHP version incompatibility, and security exposure through WebDAV auth, XML parsing such as XXE, and path handling. For production Laravel use, rely on maintained sabre/dav and perform your own security review.
- How should I test a WebDAV integration in Laravel if I use sabre/dav instead of this bundle?
- Write integration tests covering PROPFIND, GET, PUT, MKCOL, LOCK, UNLOCK, and authentication failures against your Laravel route. Use Laravel's HTTP testing tools or instantiate the SabreDAV server directly in tests with a minimal filesystem backend. Test plugin ordering, principal resolution, and any ACL or tenancy rules before adding CalDAV or CardDAV if those features are required.
Weaver
How can I help you explore Laravel packages today?