Skip to the content
Documentation

WebDAV

No ratings yet

Exponential has a built-in WebDAV server. A WebDAV client (a file manager that can connect to a WebDAV address, or a command line client) shows the content tree of a siteaccess as folders and files: you can browse it, upload files and images as new content, download them, and rename, move and remove content, as far as your role allows.

How it works

  • The server is the script index_webdav.php in the installation root (its old name webdav.php still forwards to it and logs a deprecation warning). Clients connect to https://www.example.com/index_webdav.php/<siteaccess>/, or to a host of its own that sends every request to the script.
  • The top folder lists the siteaccesses of site.ini [SiteSettings] SiteList[]. Below a siteaccess, the tree starts at webdav.ini [GeneralSettings] StartNode (node 2 by default).
  • The client signs in with an Exponential user name and password. The user needs user/login for that siteaccess and the content policies for what it does (content/read, create, edit, remove).
  • Objects of the classes in FolderClasses[] are shown as folders. Other objects are shown as files: an uploaded file becomes an object of the class that upload.ini chooses for its MIME type.

Settings

# settings/override/webdav.ini.append.php
[GeneralSettings]
# the master switch, off by default
EnableWebDAV=true
# write every request to var/log/webdav.log
Logging=disabled
# the node the tree starts at
StartNode=2
# classes always shown as folders
FolderClasses[]
FolderClasses[]=folder

[FolderSettings] FolderClass is deprecated: WebDAV uses upload.ini to choose the class of new folders and files.

Two-step sign-in

WebDAV clients cannot answer a second sign-in step. By default an account for which the site requires one signs in over WebDAV with its password alone. A site can opt WebDAV in with sevenxauthentication2fa.ini [OtherSignInPaths] Guard[]=webdav; such an account then signs in with an app password made for WebDAV on its two-step sign-in page. See Second factor on other sign-in paths.

Limits

  • An uploaded file becomes an object of the class upload.ini [CreateSettings] MimeClassMap[] names for its MIME type, or of DefaultClass (file) when none does.
  • Use HTTPS: the password is sent with every request.

Related pages

In this section

Contributors

Comments (7 historical)

Written by readers of the earlier documentation sites, kept as they were.

  1. WebDAV and Clustering

    Stephen Paschall ·

    Note: As of this writing, WebDAV has not been updated to support the new "clustering" architecture eZ's rolled out. WebDAV still stores binaries in the file system rather than in the DB.

  2. Uploading limit

    Pedro Alvarez Gonzalez ·

    I don't know if PHP uploading limit affects WebDAV module.

  3. small typo in given example

    Gaetano ·

    the folder where extensions are stored is named "extension", not "extensions"

  4. .htaccess

    Ken ·

    Hi,
    Do you mind showing the .htaccess-file that's rewrite?
    webdav.ez.no -> webdav.php
    I'm having problems with when I access webdav.domain.no, I get 400 "Bad Request"
    But when I'm access www.domain.no/webdav.php it looks to be answering right, but of cource won't work because of the other rewriteCond.
    Version 4.0.1
    Kind regards from
    Ole-Kenneth, Norway

  5. What about windows7 ?

    Vytautas Germanavičius ·

    I tried to use solution for vista, but it do not help me to connect from windows 7...

Comments

Add a comment

Comments are read by a moderator before they appear.