I have not played with those products but I have examined them and believe that Sharepoint uses an ISAPI filter to re-route the webdav requests to and from IIS to it's virtual file system. That's basically what I wanted to do. But I suppose if we could build a webdav server with APACHE that would work equally well as long as it ran on Win2k and 2003. I don't necessarily need to run it through IIS if I ship my own web server to do this function. The only issue will be programmatically configuring it so that I can run them both on port 80 on the same box, but with different host headers. I will check out the apache resources. Thanks for the info. Steve West Lead Architect - ProjectInsight.net Web-Based Project Management Software http://www.projectinsight.net

I'd like to see if anyone out there has any experience in catching webdav requests to IIS and redirecting them to an ASPX page for processing. IIS handles webdav requests, but only allows you webdav on a physical windows file system. I'd like to intercept the requests and present my own custom file system to the user. Anyone done anything like this? Steve West Lead Architect - ProjectInsight.net Web-Based Project Management Software http://www.projectinsight.net

Where is this coming from? avneeshb wrote: System.Web.DirectoryMonitor.AddFileMonitor(String file) +429 System.Web.DirectoryMonitor.StartMonitoringFile(String file, FileChangeEventHandler callback, String alias) +76 System.Web.FileChangesMonitor.StartMonitoringPath(String alias, FileChangeEventHandler callback) +495 System.Web.Caching.CacheDependency.Init(Boolean isPublic, Boolean isSensitive, String[] filenamesArg, String[] cachekeysArg, CacheDependency dependency, DateTime utcStart) +1535 System.Web.Caching.CacheDependency..ctor(Boolean isSensitive, String[] filenames, DateTime utcStart) +50 System.Web.Configuration.HttpConfigurationSystem.GetCacheDependencies(Hashtable cachedeps, DateTime utcStart) +144 System.Web.Configuration.HttpConfigurationSystem.ComposeConfig(String reqPath, IHttpMapPath configmap) +697 System.Web.HttpContext.GetCompleteConfigRecord(String reqpath, IHttpMapPath configmap) +434 System.Web.HttpContext.GetCompleteConfig() +49 System.Web.HttpContext.GetConfig(String name) +195 System.Web.CustomErrors.GetSettings(HttpContext context, Boolean canThrow) +20 System.Web.HttpResponse.ReportRuntimeError(Exception e, Boolean canThrow) +39 System.Web.HttpRuntime.FinishRequest(HttpWorkerRequest wr, HttpContext context, Exception e) +486 It looks to me like you are possibly handling the invalid request and that the folder path is is not clean for the start monitoring path. Is this IIS code? It looks like your code. I just tried a "~" on my system where we handle invalid URL's through the error page and it didn't create any errors. Steve West Lead Architect - ProjectInsight.net Web-Based Project Management Software http://www.projectinsight.net

The way we have implemented an incorrect link before was by implementing a custom 404 error site /Errors/404.aspx, and setting IIS to redirect to the 404 page. This allows us to have a link to an item say www.someurl.com/Guid... the 404 is fired and in the 404 we see if a Guid was supplied, if so we look it up and redirect the user to that item. I think it's easier to catch 404 errors using the IIS settings than it is to try to catch the 404 in the Global.asax. I think this is what you are asking. Steve West Lead Architect - ProjectInsight.net Web-Based Project Management Software http://www.projectinsight.net