Changes

Jump to navigation Jump to search
1,844 bytes added ,  10:29, 3 August 2022
m
Text replacement - "8984" to "8080"
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 [httphttps://en.wikipedia.org/wiki/Webdav 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.  The implementation in BaseX is based on the [http://milton.io Milton library]. Currently, only Basic Authentication is supported.
=Usage=
By default, the BaseX HTTP server makes the WebDAV service is activated and is accessible at {{Code|http://localhost:89848080/webdav/}}. Generally it If no default credentials are specified, they will be requested by the client ([[Web Application#User Management|see further]]). It can be accessed using by either with a <code>http:&#47;&#47;<httphost>:<httpport>/webdav/</code> or <code>webdav://<httphost>:<httpport>/webdav/</code> URL, depending on your 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). =Authentication= The WebDAV service uses the database user credentials to perform authentication and authorization. A default user can be defined in the configuration [[Web Application#Authentication|as described here]]. =Root Directory= In the used WebDAV clientroot directory, all existing databases are listed. As new resources can only be stored inside a database, it is not possible to store files in the root directory. If a file is copied on top level, a new database will be created, which contains this resource. =Resources= ==XML Documents== Uploaded files that start with an angle bracket will be stored as XML files. XML entities will be decoded during this process. If a file is downloaded, the characters with the following code points will be encoded as entities: * 160 (non-breaking space)* 8192–8207, 8232–8239, 8287–8303 (see [https://en.wikipedia.org/wiki/General_Punctuation General Punctuation]) ==Binary Files== If XML parsing files, or if the first character of the input is no angle bracket, the file will be stored as binary resource=Locking=
=Authorization=The BaseX WebDAV implementation supports locking. It can be utilized with clients which support this feature (e.g. [[oXygen|oXygen Editor]]). [https://tools.ietf.org/html/rfc4918#section-6.2 EXCLUSIVE and SHARED] locks are supported, as well as [https://tools.ietf.org/html/rfc4918#section-7 WRITE] locks.
The '''Note:''' WebDAV service uses the locks are stored in a database user credentials in order to perform authentication and authorizationcalled <code>~webdav</code>. If the database user and password are explicitly specified when starting is deleted, it will automatically be recreated along with the BaseX HTTP Server using the corresponding [[Startup_Options#BaseX_HTTP_Server|startup options]]next lock operations. If a resource remains locked, WebDAV will not request additional user authentication from it can be unlocking by removing the clientcorrespondent <code><w:lockinfo></code> entry.
=WebDAV Clients=
Please check out the following tutorials to get WebDAV running on different operating systems and with oXygen:
* [[WebDAV: Windows 7|Windows 7and up]]
* [[WebDAV: Windows XP|Windows XP]]
* [[WebDAV: Mac OSX|Mac OSX 10.4+]]
=Changelog=
 
;Version 7.7
* Added: [[#Locking|Locking]]
;Version 7.0
* WebDAV API introduced
 
[[Category:HTTP]]
Bureaucrats, editor, reviewer, Administrators
13,554

edits

Navigation menu