![set up a webdav server for marklogic set up a webdav server for marklogic](https://docs.marklogic.com/media/apidoc/10.0/guide/monitoring/history/images/doc-disk-detail-aggregate.gif)
Simple HTTP clients use only a subset of the methods necessary to properly interact with a WebDAV application server It is recommended that you only use a WebDAV specific client against a MarkLogic WebDAV application server. WebDAV (Web Distributed Authoring and Versioning) is an extension of the HTTP protocol that allows to manage files on a remote server, access documents over the web and collaboratively work on them. For example, if a request to create collection /a/b/c/d/ is made, and neither /a/b/ nor /a/b/c/ exists, the request must fail." Note that the MarkLogic server has three types (at least) of application servers that can be created and managed from the server management and administration page: HTTP, XDBC and WebDAV For the XDBC host and port in the Oxygen connection make sure you use the port of an XDBC application server(not HTTP server).
![set up a webdav server for marklogic set up a webdav server for marklogic](https://image.slidesharecdn.com/d9e0c290-7e81-4896-901e-6e41f1031dbf-161004035355/95/marklogic-course-3-638.jpg)
The WebDAV RFCÂ states: "When the MKCOL operation creates a new collection resource, all ancestors must already exist, or the method must fail with a 409 (Conflict) status code. In order to insert a document into a directory that does not exist, the WebDAV client needs to use these HTTP methods to check if the directory exists (PROPFIND), create the directory (MKCOL / PUT), and then insert the document (PUT). These extra methods include MKCOL, PROPFIND, and COPY. In setup.xqy, the setup:configure-server() function uses the same options for HTTP and WebDAV app servers, resulting in this error: ERROR: ADMIN-INVALIDCONFIG: (err:FOER0000) Invalid configuration: modules is not a configurable element f. I try to send continue (HTTP/1.1 100 Continue) but this didnt works. Application-level authentication is available on HTTP and WebDAV servers. Hello Im doing a webdav server for a internet explorer client and I have a problem when the client sends put for create a new resource because it dont sends the body. Any users accessing the server automatically inherit the security attributes (roles, privileges, default permissions) of the default user. The purpose of WebDAV application servers in MarkLogic is to support the additional HTTP methods provided by the WebDAV RFC. Use the Admin Interface to specify a default user and set its permissions. Either of these tools is a great way of getting up and running with MarkLogic Server. Customers will sometimes run into strange issues when submitting requests to a WebDAV application server from HTTP clients. It can validate your XQueries using MarkLogic's validator (so it picks up knowledge of MarkLogic-specific functions, etc.), and it can run those queries on MarkLogic Server and return the results, just as easily as Eclipse.