help.axcms.netAxinom Logo
Save Save Chapter Send Feedback

Configuring AxCMSWebDav on IIS 7.x



Installing WebDAV 7.5 for IIS

Configuring AxCMSWebDAV


Installing WebDAV 7.5 for IIS

Installing for IIS 7.0

IIS 7.0 users (Windows Vista, Windows Server 2008) need to install WebDAV package additionally.

There are two separate downloadable packages for the new WebDAV extension module; you need to download the appropriate package for your version of Windows:

You must run the installation package as an administrator.

For additional installation help please proceed to the official IIS 7 guide:


Installing for IIS 7.5

IIS 7.5 users (Windows 7, Windows Server 2008 (R2)) need to add WebDAV from Server Manager.

Go to Start - Server Manager, scroll down to Web Server (IIS) role and check whether you have WebDAV Publishing installed or not. Otherwise click Add Role Services button.

In the appeared Role Services window add WebDAV Publishing



Configuring AxCMSWebDAV

AxCMSWebDav files

Ensure that you have AxCMSWebDav package under your AxCMS_PremiumSample folder



Under your AxCMSWebDav folder you should create web.config file. Here is example of working web.config for localhost (DEV) environment.

If you use this sample config file, don't forget to take a look at its content. Maybe you should change Database connection string or application URLs if you have non-standard installations.

In the end of config file there is ISAPI module mapped, if your system is 32 bit you should replace

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


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


IIS Application

Go to Internet Information Services (IIS) manager, right click on Default Web Site and create application like on pictures below:

Set application pool to Classic .NET AppPool (or other application pool with classic managed pipeline mode).


WebDAV in a productive environment

In the productive environment you normally cannot create a virtual folder directly. You have to create a virtual site first. Unfortunately you cannot place WebDAV virtual folder under the CMS virtual site. Windows Explorer seems to connect and to authenticate itself to the host part of a WebDAV URL. The Forms authentication of a CMS web application will confuse it.

if you need a whole Web Site for your WebDAV environment do next:

  1. Create Web Site pointing to some location e.g. %SystemDrive%\inetpub\wwwroot
  2. Under your Web Site create WebDAV Application pointing to C:\Projects\AxCMS_PremiumSample\AxCMSwebDAV


ISAPI application mapping

Go to Handler Mappings under your AxCMSWebDav application and add Wildcard Script Map with Request path "*" and Executable "%windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll" for 64 bit systems or "%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" for 32 bit systems


Enabling WebDAV

Under Web Site where you created AxCMSWebDav application enable WebDAV Authoring Rules




Testing WebDAV Installation

To be sure you configured WebDAV correctly, try to open it in your browser. Login with user: AxCMS\axinom, password: axinom (case sensitive). You should get XML like on picture:


Accessing WebDAV folder

You should access WebDAV from client machine. You could get authorization error if you try to access WebDAV from the server itself.

Go to your Internet Explorer browser. Expand File menu end choose Open. In the appeared window type the url of your WebDAV (http://PCname/AxCMSWebDav) and tick Open As Web Folder.

Login with (login credential is case sensitive)

User: AxCMS\axinom
Password: axinom

After you should get opened web folder like on picture

If you are expecting problems with logging then refer help form Microsoft Knowledge Base: