Problem with Wildcard Mapping in Default Web Site

[Alan Dean]

Hi,

I have a confusing problem. I have written a web application that uses
a wildcard mapping to ..\v2.0.50727\a spnet_isapi.dll with HttpModules
and HttpHandlers.

All works well when I install the application as a root web site, but
when I install the application on to the Default Web Site then it
doesn't work - I just get errors. I have tried both installing a
virtual directory and the whole default web site.

I know that my modules and handlers are not being executed as they emit
no tracing.

Had a look at the web logs, but they are not at all illuminating:

2006-11-23 21:46:49 W3SVC1 192.168.1.101 PUT
/OK_Test/9e684934-d9a3-4696-b43c-9639912149aa.rd f - 80 - 192.168.1.101
OnlineTravel.Ca cheClient/1.0 500 0 0

even when I try a simple GET on an existing file, there is an error:

2006-11-23 21:57:42 W3SVC1 192.168.1.101 GET /hello.txt - 80 -
192.168.1.101
Mozilla/4.0+(compatible ;+MSIE+7.0;+Win dows+NT+5.2;+.N ET+CLR+1.1.4322 ;+.NET+CLR+2.0. 50727)
406 0 0

the http response is no more informative:

HTTP/1.1 406 Not Acceptable
Date: Thu, 23 Nov 2006 21:57:42 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
Content-Length: 0

In case it has any effect, I have tried this with WebDAV allowed
(although this doesn't seem to be required when you create a new root
web site).

Regards, Alan Dean