Difference between revisions of "WebDAV"

From BaseX Documentation
Jump to navigation Jump to search
Line 7: Line 7:
 
By default, the WebDAV service is activated and is accessible at {{Code|http://localhost:8984/webdav/}}. Generally it can be accessed using either with a <code>http:&#47;&#47;<httphost>:<httpport>/webdav/</code> or <code>webdav://<httphost>:<httpport>/webdav/</code> URL, depending on the used WebDAV client.
 
By default, the WebDAV service is activated and is accessible at {{Code|http://localhost:8984/webdav/}}. Generally it can be accessed using either with a <code>http:&#47;&#47;<httphost>:<httpport>/webdav/</code> or <code>webdav://<httphost>:<httpport>/webdav/</code> URL, depending on the used WebDAV client.
  
Please note that the file size of XML documents will be displayed as 0 bytes, as the actual file size cannot be determined until the full document is being serialized. This may cause problems with some WebDAV clients (e.g. NetDrive or WebDrive).
+
Please note that the file size of XML documents will be displayed as 0 bytes, as the actual file size can only be determined if the full document is being returned and serialized. This may cause problems with some WebDAV clients (e.g. NetDrive or WebDrive).
  
 
=Authorization=
 
=Authorization=

Revision as of 14:14, 7 September 2013

This page presents one of the Web Application services. It describes how to use the WebDAV file system interface.

BaseX offers access to the databases and documents using the WebDAV protocol. WebDAV provides convenient means to access and edit XML documents by representing BaseX databases and documents in the form of a file system hierarchy.

Usage

By default, the WebDAV service is activated and is accessible at http://localhost:8984/webdav/. Generally it can be accessed using either with a http://<httphost>:<httpport>/webdav/ or webdav://<httphost>:<httpport>/webdav/ URL, depending on the used WebDAV client.

Please note that the file size of XML documents will be displayed as 0 bytes, as the actual file size can only be determined if the full document is being returned and serialized. This may cause problems with some WebDAV clients (e.g. NetDrive or WebDrive).

Authorization

The WebDAV service uses the database user credentials in order to perform authentication and authorization. If database user and password are explicitly specified when starting the BaseX HTTP Server using the corresponding startup options, WebDAV will not request additional user authentication from the client.

Locking

BaseX WebDAV implementation supports WebDAV locking since Version 7.7. It can be utilized with clients which support this feature (e.g. oXygen Editor). EXCLUSIVE and SHARED locks are supported, as well as WRITE locks.

Note: WebDAV locks are stored in a database called ~webdav. Implementations should not rely on the existence of the database, since it may not be accessible in the future.

WebDAV Clients

Please check out the following tutorials to get WebDAV running on different operating systems and with oXygen:

Changelog

Version 7.7
Version 7.0
  • WebDAV API introduced