WebDAV Access
Members open their files like a network drive from Explorer, Finder, Cyberduck or a phone app at /webdav, with read or write access per package. Premium.
The WebDAV Access plugin turns a member's account into a network drive. Windows Explorer, macOS Finder, Cyberduck, a Linux file manager or a phone app connects to /webdav with the member's own username and password and sees My Files as folders: browse, open, upload, download, rename, move and delete, without ever opening the website. A read-only Shared With Me folder at the root shows what other members have shared with them.
It is for sites whose members work with many files a day - photographers, agencies, teams who want the site to behave like a company drive - and for anybody who would rather drag files in Explorer than through a browser.
Switching it on
WebDAV Access is a premium plugin: it needs the webdav addon on your licence. Buy it at lcpanel.com, open Admin → Configuration → License and press Check again now so the site learns about it, then go to Admin → Extensions → Plugins (the page is called Manage Plugins) and switch WebDAV Access on. Its page then appears under Extensions in the admin menu as WebDAV Access (/admin/plugin/webdav).
As soon as it is on, two addresses answer:
| Address | What it is |
|---|---|
/webdav (and anything under it) | The WebDAV server itself. Every request carries HTTP Basic authentication. |
/webdav_access | The public guide page Mobile App & Desktop Access, with the member's own access URL, their access level and step-by-step instructions for each client. |
The guide is linked from the public Features menu as Webdav Access and from the bottom of the file manager's left rail as WebDAV, as long as Show the front-end guide page is on.
The settings
The admin page (Extensions → WebDAV Access) shows the endpoint, a link to the guide, a note about the Authorization header (see below), and these settings:
| Setting | What it does |
|---|---|
| Show the front-end guide page | Puts Webdav Access in the Features menu and WebDAV in the file manager rail. Off hides the guide; the /webdav endpoint keeps working. |
| Name of the "Shared with me" folder | The read-only folder at the root that lists shares made to this member (default Shared With Me). Empty hides it. |
| Free User access, Premium access, ... | One row per account package (Account packages): No access, Read only or Read and write. Paid, Moderator and Admin packages default to read and write, free ones to read only. |
Save with Save. The access level is checked on every request, so changing a package's row takes effect at once.
What the member sees
On /webdav_access the member finds:
- Access details - the WebDAV access URL, that their Username / password are their site login, and their Access level (Read only, Read and write, or a note that their account type has no access and an upgrade would give it).
- Desktop clients - Windows File Explorer (This PC → Map network drive → Connect to a Web site…), macOS Finder (Go → Connect to Server…), and Cyberduck.
- Mobile & tablet clients - WebDAV Nav Lite, Solid Explorer and CX File Explorer on Android; the Files app or WebDAV Navigator on iPhone and iPad.
Inside the drive, the member's folders appear exactly as in the file manager. The root also holds the Shared With Me folder (read-only, whatever the package says). Team workspaces are not part of the drive: WebDAV shows the member's own My Files only. Uploads dropped into the drive go through the normal upload_store() road, so the package's upload limits, blocked extensions and storage allowance apply, duplicates are reused, and thumbnails and conversions are queued as for any upload. Deletes move files to the trash.
The server answers OPTIONS, PROPFIND, PROPPATCH, HEAD, GET, PUT, MKCOL, DELETE, MOVE, COPY, LOCK and UNLOCK (DAV class 1 and 2), which is what Explorer and Finder expect. A member may sign in with their e-mail address instead of the username.
Server notes
The Authorization header. Under Apache with PHP as CGI or FPM, the Authorization header never reaches PHP by default, so every sign-in fails. Add one of these to .htaccess (the admin page prints the same hint):
# under the RewriteEngine On line
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
or
CGIPassAuth On
A SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1 line works too. Nginx with PHP-FPM passes the header by itself.
HTTPS. Windows Explorer refuses Basic authentication over plain http:// unless the registry value BasicAuthLevel is set to 2. Give the site a certificate and connect over https:// - it protects the password as well.
Large files. A PUT of a big file is one request, so the web server's body limits (LimitRequestBody, client_max_body_size) and PHP's post_max_size must allow it; the package's Max Upload Size is checked as well. For very large files the website's parallel upload (Uploads) is quicker.
Tips
- Keep the free package on Read only: visitors can mount the drive to fetch their files, while writing stays a premium benefit worth upgrading for.
- The access rows follow the packages: when you add a package, open the plugin page once and set its row.
- A member who changes their site password changes their WebDAV password too; two-step sign-in is not asked for over WebDAV.
- If a client shows an empty drive but no error, check Admin → System Tools → System Logs - a wrong
Authorizationsetup usually shows up there first.