Previous Next

Thread: WebDAV publishing and file extensions

Last post 05-22-2008 1:14 PM by Dotren. 6 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (7 items)

Sort Posts:

  • 05-21-2008, 4:33 PM

    • Dotren
    • Not Ranked
    • Joined on 05-21-2008, 4:10 PM
    • Posts 8
    • Dotren

    WebDAV publishing and file extensions

    Greetings,

     I'm currently learning IIS7.0 using a test server we have set up in the office to host our test version of our new website.  We use Microsoft Expression Web for our design and publishing and I've been attempting to get our company to move away from Frontpage Server Extensions. 

     We've got WebDAV installed on the server and I can publish most files normally through Expression Web but theres been a few file types I've run into where an error occurs.  The two file types I've identified so far are older Access databases (*.mdb) and web.config files.  When I attempt to publish these, it looks like its publishing but then pops up a dialog saying to check that Frontpage Server Extensions or Sharepoint Services are installed.  When I click on more details, it displays a 404 error of all things.  Other database file types are fine, even Access 2007 ones (*.accdb) but I can not publish or retrieve those other file types.  An instance of them is created on the server but no data is put into them.

     I'm wondering if anyone can tell me if this is a server issue or something with Expression Web when using WebDAV without FPSE or Sharepoint Services?  If its a server issue, what is the procedure to fix it?  We've already attempted to set the applyToWebDAV in the requestFiltering to false for the "Default Web Site" since the documentation says that by default certain file extensions are blocked but the problem has persisted.

     Any help and/or advice would be greatly appreciated!

    Thanks,
    Jason

  • 05-22-2008, 10:49 AM In reply to

    • eokim
    • Top 500 Contributor
    • Joined on 02-22-2008, 7:31 PM
    • Posts 10
    • eokim

    Re: WebDAV publishing and file extensions

    It looks like <requestFiltering> prohitbit your request.

    1. Open up %windir%\system32\inetsrv\config\applicationHost.confg

    2. Find the section system.webServer/security/requestFiltering. Then, find sub element <fileExtensions> and <hiddenSegments>

    At this point, you have two choices.

    1) Set attribute applyToWebDAV = 'false' to bypass requestFiltering with WebDAV request for both <fileExtensions> and <hiddenSegments> elements.

    ex) 

    <fileExtensions allowUnlisted="true" applyToWebDAV="false">

    <hiddenSegments applyToWebDAV="false">

     

    2) Explicitly turn off filtering for .mdb and web.config

    ex) 

    <fileExtensions allowUnlisted="true" applyToWebDAV="true">

      <add fileExtension=".mdb" allowed="true" />

    ...

     <hiddenSegments applyToWebDAV="true">

       <remove segment="web.config" />

     

    Please, note that if you take 2), all http requests are affected. But, 1) is only for WebDAV request.

  • 05-22-2008, 10:55 AM In reply to

    • eokim
    • Top 500 Contributor
    • Joined on 02-22-2008, 7:31 PM
    • Posts 10
    • eokim

    Re: WebDAV publishing and file extensions

  • 05-22-2008, 11:06 AM In reply to

    • Dotren
    • Not Ranked
    • Joined on 05-21-2008, 4:10 PM
    • Posts 8
    • Dotren

    Re: WebDAV publishing and file extensions

    Thanks for the response eokim.

     Yeah we found that article the other day when looking for solutions and I'm fairly certain we implemented this with no effect.

    I'm going to remote in and double check now though.  I'll post back when I have something.

    Thanks!

  • 05-22-2008, 12:13 PM In reply to

    • Dotren
    • Not Ranked
    • Joined on 05-21-2008, 4:10 PM
    • Posts 8
    • Dotren

    Re: WebDAV publishing and file extensions

    Ok, here is what I've run into.

     I went ahead and cleared out the options we put into the applicationHost config file before and ran those commands on that link again... the results are:

    <requestFiltering>
             <fileExtensions applyToWebDAV="false" />
             <hiddenSegments applyToWebDAV="false" />
             <verbs applyToWebDAV="false" />
    </requestFiltering>

     This is in the Default Web Site settings and not in the global settings.

     Now, I retested uploading a web.config file to the root and success!  Unfortunately, I can't seem to upload a .config file to any of the sub directories though (which of course is handy to do for fine tuning settings in sub directories).  I'm getting the same "make sure FPSE or Sharepoint Services are installed" (which I find to be a funny error since Expression Web is telling me you can't actually use WebDAV to connect to a site with either of those installed) but this time the Details button gives me "Bad Request".

     Thanks

  • 05-22-2008, 12:35 PM In reply to

    • eokim
    • Top 500 Contributor
    • Joined on 02-22-2008, 7:31 PM
    • Posts 10
    • eokim

    Re: WebDAV publishing and file extensions

    Your setting seems to be OK.

    One thing I can think of the problem you're facing is that you should make sure web.config file you're uploading is valid against schema and welformed xml. If not, server rejects request with 400 Bad Request.

     

  • 05-22-2008, 1:14 PM In reply to

    • Dotren
    • Not Ranked
    • Joined on 05-21-2008, 4:10 PM
    • Posts 8
    • Dotren

    Re: WebDAV publishing and file extensions

    I just tried copying the web.config I'm able to successfully publish/upload in the root to one of the sub-directories and attempted to publish and no luck.  It's still giving me the Bad Request.

    Technically I know of ways I can work around this, setting individual location rules in the root web.config to allow different rules for the sub-directories for example but now its just bugging me.  Plus, I'm trying to learn IIS7 at the same time so it does help to troubleshoot until I understand the issue.

    Thanks

Page 1 of 1 (7 items)
Page view counter