Kentico CMS 7.0 Developer's Guide

Configuration for WebDAV

Configuration for WebDAV

 Previous topic Next topic Mail us feedback on this topic!  

Configuration for WebDAV

 Previous topic Next topic JavaScript is required for the print function Mail us feedback on this topic!  

The following steps need to be taken in order to install a Kentico CMS website with WebDAV support enabled. The beginning of the procedure is different for IIS 7.0 or higher and the previous versions of IIS.

 

Step 1 on IIS versions prior to 7.0

 

Before you start, it is necessary to have a website created in the IIS root (i.e. not in a virtual directory). The website should have Windows authentication enabled in IIS.

 

1. Launch Kentico Web Installer. In step 2, choose I want to use local IIS server. In step 3, use the following configuration:

 

•Choose web site: choose the website that you have prepared in the IIS root

•Choose target folder: enter the path to the website's physical folder

•This is an installation to the root (do not create virtual directory): enabled

 

Click Next and proceed through the rest of the wizard.

 

devguide_clip1324

 

When using IIS versions older than 7.0, it is also necessary to correctly map the aspnet_isapi.dll file in IIS. The process of performing this configuration is described below.

 

Configuration for IIS 5 and earlier versions

 

Open the IIS Management console, right‑click on your Kentico application in the tree and select Properties. On the Home Directory tab, click Configuration and then Add to create a new application extension mapping. Enter the following details into the dialog:

 

•Executable: <Windows install directory>\Microsoft.NET\Framework\<.Net framework version>\aspnet_isapi.dll

•Extension: .*

•Verbs: All Verbs

•Check that file exists: disabled

 

devguide_clip1494

 

Click OK and return to the main management console. Now right‑click the website under which your application is stored and select Properties. Switch to the Home directory tab, ensure that the Read box is checked and set the Execute permissions field to Scripts only.

 

Configuration for IIS 6

 

Open the IIS 6 Management console, right‑click on your Kentico application in the tree and select Properties. On the Home Directory tab, click Configuration and then Insert to add a new wildcard application map. Enter the following details into the dialog:

 

•Executable: <Windows install directory>\Microsoft.NET\Framework\<.Net framework version>\aspnet_isapi.dll

•Verify that file exists: disabled

 

devguide_clip1542

 

Click OK and return to the main management console. Now right‑click the website under which your application is stored and select Properties. Switch to the Home directory tab, ensure that the Read box is checked and set the Execute permissions field to Scripts only.

 

Step 1 on IIS 7.0 or higher

 

On IIS 7.0 or higher, you do not need to have the website created in the IIS root - it can also be installed in a virtual directory.

 

1. Launch Kentico Web Installer and proceed through the steps with configuration according to your needs.

 

If you wish to run the website using an application pool set for Classic managed pipeline mode, please ensure that your web.config file contains the two Isapi extension handlers highlighted below once the Web installer finishes.

 

The handlers should be defined as follows on .NET 3.5:

 

...
<!-- WebDAV location BEGIN -->

<location path="cms/files">

 <system.web>
   <httpHandlers>
     <clear />
     <add verb="*" path="*" type="CMS.WebDAV.WebDAVHandler, CMS.WebDAV" />
   </httpHandlers>
   <httpRuntime executionTimeout="2400" maxRequestLength="2097151" />
 </system.web>
 <system.webServer>
   <handlers>
     <clear />

<add name="aspnet_isapi 32-bit" path="*" verb="*" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv2.0,bitness32" />
<add name="aspnet_isapi 64-bit" path="*" verb="*" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv2.0,bitness64" />

     <add name="CMSWebDAVHandler" path="*" verb="*" type="CMS.WebDAV.WebDAVHandler, CMS.WebDAV" />
   </handlers>
   <security>
     <requestFiltering>
       <requestLimits maxAllowedContentLength="2147483648" />
     </requestFiltering>
   </security>
 </system.webServer>
</location>
<!-- WebDAV location END -->

...

 

On .NET 4.0, the handlers should be defined the following way:

 

...
<!-- WebDAV location BEGIN -->

<location path="cms/files">

 <system.web>
   <httpHandlers>
     <clear />
     <add verb="*" path="*" type="CMS.WebDAV.WebDAVHandler, CMS.WebDAV" />
   </httpHandlers>
   <httpRuntime executionTimeout="2400" maxRequestLength="2097151" />
 </system.web>
 <system.webServer>
   <handlers>
     <clear />

<add name="aspnet_isapi 32-bit" path="*" verb="*" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv4.0,bitness32" />

<add name="aspnet_isapi 64-bit" path="*" verb="*" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv4.0,bitness64" />

     <add name="CMSWebDAVHandler" path="*" verb="*" type="CMS.WebDAV.WebDAVHandler, CMS.WebDAV" />
   </handlers>
   <security>
     <requestFiltering>
       <requestLimits maxAllowedContentLength="2147483648" />
     </requestFiltering>
   </security>
 </system.webServer>
</location>
<!-- WebDAV location END -->

...

 

If necessary, adjust the path in the scriptProcessor attributes of the handlers according to your current .NET framework version.

 

The rest of the configuration - common for all IIS versions

 

2. When the web installation is complete and the appropriate configurations have been made according to your IIS version and application pool mode, open the website using the link in the last step of the Web installer. When you access the URL, Kentico CMS Database Setup will be displayed. Follow the wizard as described in Installation and deployment -> Installation procedure -> Database setup.

 

3. After finishing the Database Setup, go to Site Manager -> Settings -> Integration -> WebDAV and configure the settings as described in the Settings topic.

 

4. The last step is to enable Windows authentication for your website. Please follow the instructions in Development -> Membership -> Authentication -> Windows authentication -> Configuring Windows authentication.

 

With all these steps performed, WebDAV editing should be possible. Please refer to the Editing files using WebDAV topic to learn more about the editing possibilities.