Changes

Jump to navigation Jump to search
200 bytes removed ,  10:29, 3 August 2022
m
Text replacement - "8984" to "8080"
=Usage=
By default, the BaseX HTTP server makes the WebDAV service accessible at {{Code|http://localhost:89848080/webdav/}}. If no default credentials are specified, they will be requested by the client ([[Web Application#User Management|see further]]). It can be accessed by either <code>http:&#47;&#47;<httphost>:<httpport>/webdav/</code> or <code>webdav://<httphost>:<httpport>/webdav/</code>, 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).
=AuthorizationAuthentication=
The WebDAV service uses the database user credentials in order to perform authentication and authorization. Initial A default user name and password are both set to <code>admin</code>. If database user and password are explicitly specified when starting can be defined in the BaseX HTTP Server using the corresponding configuration [[Command-Line OptionsWeb Application#BaseX_HTTP_ServerAuthentication|startup optionsas described here]], WebDAV will not request additional user authentication from the client.
=Root Directory=
* 160 (non-breaking space)
* 8192–8207, 8232–8239, 8287–8303 (see http[https://wwwen.w3schoolswikipedia.comorg/charsetswiki/ref_utf_punctuation.aspGeneral_Punctuation General Punctuation])
==Binary Files==
=Locking=
The BaseX WebDAV implementation supports locking. It can be utilized with clients which support this feature (e.g. [[oXygen|oXygen Editor]]). [httphttps://tools.ietf.org/html/rfc4918#section-6.2 EXCLUSIVE and SHARED] locks are supported, as well as [httphttps://tools.ietf.org/html/rfc4918#section-7 WRITE] locks.
'''Note:''' WebDAV locks are stored in a database called <code>~webdav</code>. If the database is deleted, it will automatically be recreated along with the next lock operations. If a resource remains locked, it can be unlocking by removing the correspondent <code><w:lockinfo></code> entry.
Bureaucrats, editor, reviewer, Administrators
13,554

edits

Navigation menu