WebDAV Protocol
Use
Generally, access to resources (documents, folders, and links) in Content Management is performed by a WebDAV servlet. All Content Management operations on documents and folders, such as the displaying and storing of content and properties, the locking and unlocking of resources, and so on, are performed by methods that conform to the WebDAV protocol.
WebDAV (Web-based Distributed Authoring and Versioning) comprises a set of extensions to the HTTP protocol that allow users to collaboratively edit and manage files on remote Web servers. For more information, see WebDAV.
Integration
The WebDAV protocol is used to access resources regardless of the particular repositories in which they are located. Among other things, this is needed in order for the WebDAV repository manager to function correctly.
Features
The WebDAV protocol can be configured in various respects as described in the table below.
Parameters of the WebDAV Protocol
Parameter |
Required |
Description |
Allow Depth Infinity |
No |
Determines whether PROPFIND calls with depth infinity are allowed. By default, this parameter is deactivated. |
Auto Version |
No |
Determines whether PUT and PROPPATCH generate a new version of a resource if the resource is not checked out. This allows non-DeltaV-aware clients to operate alongside a DeltaV server. By default, this parameter is activated. |
Enable WebDAV Server |
No |
Determines whether support of the WebDAV protocol as specified in RFC 2518 is enabled. If it is disabled, only GET, HEAD, PUT, DELETE, and OPTIONS calls are processed. By default, this parameter is activated. |
Expected Checkin-URI |
No |
Determines whether CHECKIN and CHECKOUT generate and honor the ‘expectedcheckinuri’ element in requests. By default, this parameter is activated. |
Extension ACL |
No |
Specifies whether support for the WebDAV ACL extension is activated. By default, this parameter is activated. |
Extension dasl |
No |
Specifies whether support for the WebDAV DASL extension is activated. By default, this parameter is activated. |
Extension deltav |
No |
Specifies whether support for the WebDAV DeltaV extension is activated. By default, this parameter is activated. |
Extension Ordering |
No |
Specifies whether support for the WebDAV sorted collections extension is activated. By default, this parameter is activated. |
Extension Redirect Ref |
No |
Specifies whether support for the WebDAV redirect links extension is activated. By default, this parameter is activated. |
Force Text Download |
No |
Determines whether you are allowed to open files containing executable scripts stored in the KM repositories with your Web browser. If selected, the system does not allow you to open files containing executable scripts with your Web browser, thus preventing the execution of potentially malicious scripts. Instead, when trying to open the file with a Web browser, you are prompted to choose between the following options: ● Open the file for editing ● Download the file locally ● Cancel the operation By default, this parameter is deactivated. |
Get Collection |
No |
Collections normally do not have content. This parameter determines whether the servlet generates content, for example, an HTML page listing the children of the collection. By default, this parameter is deactivated. |
Get Extensions |
No |
Determines whether various extensions to GET, specified in query parameters on the root collection, are supported. By default, this parameter is activated. |
Include All Properties |
No |
Determines whether PROPFIND ‘allprop’ requests honor an optional ‘include’ element that specifies additional properties. By default, this parameter is activated. |
MS Web Folder Extensions |
No |
Determines whether additional properties such as DAV:ishidden are generated for Microsoft Web directory clients. By default, this parameter is activated. |
Typed Properties |
No |
Determines whether PROPFIND/PROPPATCH honors the typed properties extension where the type of properties is indicated as an attribute in the relevant XML element tag. By default, this parameter is activated. |
gzip Response |
No |
Determines whether the servlet gzips response bodies if the client announces its willingness to accept them. By default, this parameter is deactivated. |
Max WebDAV Request Size |
No |
Specifies the maximum size of a request in bytes. |
Exclude paths from WebDAV access |
No |
Comma-separated list of paths that cannot be accessed with a WebDav client. If a path specification ends in /*, the entry only excludes subfolders of the specified path. The location immediately before /* is accessible. Examples: /foo/* prevents access to all subfolders of /foo while allowing access to /foo itself. /foo prevents access to /foo, but you can still access subfolders (for example, /foo/subfoo) if you know their names. /foo, /foo/* are the only entries that prevent access to both /foo and all of its subfolders. If your portal has a large number of users, SAP recommends that you exclude the /userhome directory from WebDAV access. Otherwise, an attempt to access the directory can cause unnecessary system load. To exclude this directory, enter the following as the parameter value: /userhome |
Restrict WebDAV to Specific Roles |
No |
Comma-separated list of roles that are allowed to use the WebDAV functions. Roles that are not entered do not receive access through the WebDAV client. All HTTP methods apart from OPTIONS,GET, HEAD, DELETE, and PUT are locked. For example,
pcd:portal_content/administrator/ If you do not specify any roles, all roles have permission. |
Activities
The WebDAV protocol is pre-configured in the standard configuration. Normally, you do not need to change its configuration.
To check or modify the configuration, choose Content Management ® Protocols ® WebDAV.