DAV Maintenance tutorial
DAV Security Model DAV Maintenance & Security

## Preliminaries

- A resource has a group and an owner user, just like files in a Unix file system.
- A resource has flags determining the read, write, and execute privileges of it's owner, other members of the owner's group, and all other users on it.
- Additionally it has a free text indexing flag.
- Collections are resources also. These have the same flags but the free text index flag is treated differently.

- DAV server asks for authentication in the following situations:

  - on the read operation if URL is not public readable
  - on the write operations if URL is not public writable
- The read operations are GET, POST, PROPFIND, HEAD
- The write operations are LOCK, PUT, MOVE, COPY, DELETE, PROPPATCH
- The Webdav admin account has full access rights to the Webdav repository, regardless of privilege flags.
- The server will try to match the user to resource owner, second match to the group ownership, and last to the additional groups membership.
- If the URL is public readable, the request will be processed without asking for authentication.
- The special flag in permissions can be set to the no-index, index, index recursively.
- On resources, the last two settings act in the same way: if the resource is a text document, the content will be free text indexed, otherwise not.
- On collections, the 'no-index' will stop indexing of all direct and indirect members.
- The 'index this' flag will cause indexing only over direct members (resources).
- The 'index recursively' will allow free-text indexing of all direct and indirect members.
- The values indicated in the WebDAV content management UI are N, T and R for the no-index, index, index recursively respectively.