Configuring IIS7 to server both a wildcard ISAPI DLL and static files?

We had the same problem, then we just added these: add name="aspnet_isapi 32-bit" path="*" verb="*" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft. NET\Framework\v2.0.50727\aspnet_isapi. Dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv2.0,bitness32" /> NET\Framework64\v2.0.50727\aspnet_isapi.

Dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv2.0,bitness64.

We had the same problem, then we just added these.

This totally solved a problem I was having with Vista 64bit. Thanks! – YeahStu Sep 30 '09 at 16:08.

I have an ISAPI DLL that is configured in IIS for wild card mapping. When a request URL corresponds to a static file, I want IIS's StaticFileModule to serve that file. When the file doesn't exist, I want the ISAPI DLL to handle it.

The handlers section of my web. This works for the requests intended for the ISAPI DLL but static files are returned as 404. If I reverse the order, I just get blank pages with no content for any requests.

If I remove the ISAPI DLL from web. Config, static files are correctly served but, of course, then the ISAPI requests aren't served. My understanding is that cascading wild card handlers should work but the Microsoft docs that I can find are very vague about how to make this happen.

It is possible that this is either a configuration problem or a problem with the ISAPI DLL implementation but at this point I have no idea.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions