« Previous Next »

Thread: WebDAV on Virtual directory only doesn't work?

Last post 10-28-2009 12:06 PM by ip-rob. 2 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (3 items)

Sort Posts:

  • 10-26-2009, 2:36 PM

    • ip-rob
    • Not Ranked
    • Joined on 10-26-2009, 2:34 PM
    • Posts 3

    WebDAV on Virtual directory only doesn't work?

    I've been able to successfully publish an entire web site using WebDAV and IIS7 (Server 2008 R2) without issue.  What I want to do, however, is only have WebDAV available on a subweb (virtual directory or separate application).  This does not seem to work.

     Mapping a drive from a Win7 client to the root web site works without issue.  Mapping to a subweb (e.g. https://test.microsoft.com/webdav) always fails.

     I'm sure I'm doing some simple thing wrong but I cannot find out what it is.  Isn't is possible to just have WebDAV on a subfolder?

  • 10-27-2009, 11:04 AM In reply to

    • ip-rob
    • Not Ranked
    • Joined on 10-26-2009, 2:34 PM
    • Posts 3

    Re: WebDAV on Virtual directory only doesn't work?

    Has anyone else had an issue with no WebDAV on the main web site and WebDAV on a subweb?  I thought this would be a simple thing I'm missing...

     

  • 10-28-2009, 12:06 PM In reply to

    • ip-rob
    • Not Ranked
    • Joined on 10-26-2009, 2:34 PM
    • Posts 3

    Resolved: WebDAV on Virtual directory only doesn't work?

    The issue was several-fold and I came across the solution from another post here.

    1. WebDAV has to be enabled on the parent although no authoring rules are required.  That will prevent access to the parent.

    2. The application pool needed to run under an account that had access to the webdav folder.  This is because the web.config is housed in the folder.  The account needs to have logon as a batch rights to the server as any custom account for IIS app pools requires.

    3. The top-level folder required a classic ASP application pool so the webdav folder needed to have a separate application pool running under the native mode.

    The site is using the IIS redirect module to redirect http to https.  This did not need to be turned off for it to work.

     

Page 1 of 1 (3 items)
Microsoft Communities