Web-based Distributed Authoring and Versioning (WebDAV) is a set of extensions to the HTTP protocol. This allows you to edit and manage files on remote Web servers.
iChain supports the use of WebDAV; however, there are limitations. iChain cannot rewrite hostname references in binary data. Use the option “Forward host name sent by the browser to the Web server”.
If the client to the WebDAV application is not a browser, you must enable the settings: Allow Authentication through HTTP Authorization Header, and Use Basic/Proxy Authentication in the Authentication Profile used by the accelerator. Otherwise, the application will not work.
If you are using an iChain accelerator for WebDAV connections to NetStorage, the Allow Authentication through HTTP Authorization Header and the Use Basic/Proxy Authentication options must be enabled in the Authentication Profile used by the accelerator. Users are required to provide login credentials both for iChain and for NetStorage authentications; however, if the workstation has the NetIdentity client installed and configured to trust the NetStorage CA, the user is not prompted for the additional login to NetStorage.
The Authentication profile option, Allow Authentication through NetIdentity, might give unexpected results if you enable it in addition to basic/proxy authentication. If you enable the Allow Authentication through NetIdentity option, the workstations with the NetIdentity client installed are unable to make WebDAV connections through the accelerator. This problem occurs because the WebDAV OPTIONS header is a non-redirectable request. In this case, iChain returns a 409 Conflict error, resulting in a failed authentication and connection.