3.10. WebDAV configuration

The embedded WebDAV server lets you configure some parameter via exo.properties file. See Configuration overview if have not created this file.

# JCR Webdav configuration
exo.webdav.def-folder-node-type=nt:folder
exo.webdav.def-file-node-type=nt:file
exo.webdav.def-file-mimetype=application/octet-stream
exo.webdav.update-policy=update
exo.webdav.auto-version=checkout
exo.webdav.folder-icon-path=/eXoWCMResources/skin/images/file/nt-folder.png
exo.webdav.cache-control=text/*:max-age=3600;image/*:max-age=1800;application/*:max-age=1800;*/*:no-cache

The values you see in the code above are the default values. Here is a brief description of each parameter:

`exo.webdav.def-folder-node-type`	Default (JCR) node type which is used for the creation of collections.
`exo.webdav.def-file-node-type`	Default (JCR) node type which is used for the creation of files.
`exo.webdav.def-file-mimetype`	A mime-type is detected by file extension or HTTP request header. If those are not found, this parameter is used.
`exo.webdav.update-policy`	This defines the behavior when a PUT command is executed against an existing resource: `add`: It tries to add new resource with the same name. `create-version`: It creates a new version of the resource. Otherwise, the PUT command updates the resource and its last modification date.
`exo.webdav.auto-version`	This determines how the service responds to a request that attempts to modify a checked-in version-controlled file content. `checkout-checkin`: the request is automatically preceded by a checkout and followed by a checkin operation. `checkout`: the request is automatically preceded by a checkout operation.
`exo.webdav.folder-icon-path`	The default path is an icon in eXoWCMResources webapp.
`exo.webdav.cache-control`	This determines the live time of the caches for each type of responses. Use no-cache if you want a type to be not cached.

See more information in eXo JCR Reference, WebDAV.

See also