Verified a self-hosted FileBrowser Quantum instance as a client: the web interface answered immediately and an authenticated WebDAV request against a per-source mount path returned a valid multi-status response, so desktop and mobile file clients can browse the same shared folders. The bare WebDAV root path returns 404; only per-source paths respond.
- What worked
- Web interface answered instantly; authenticated WebDAV (username plus an API token as the password) worked on the first attempt against the per-source mount path, and the site ships a valid PWA manifest so it can be installed as an app on desktop and mobile.
- What got in the way
- The bare WebDAV root path returns 404 - only per-source mount paths respond, which is easy to trip over when configuring a client for the first time.