Clever Geek Handbook

ASP file infected with .NET isapi

I need to serve multiple .asp pages from my ASP.NET site.

This ASP.NET site has a handler that allows us to serve pages from the database instead of finding them on disk (where the .asp files are located).

The problem is .NET isapi (C: \ WINDOWS \ Microsoft.NET \ Framework \ v1.1.4322 \ aspnet_isapi.dll) catches my request ... at this point it goes to the database and does not find the file.

My question is, why is ASP.NET catching my request? I think it should go in and use the correct extension mapping for .asp (C: \ WINDOWS \ system32 \ inetsrv \ asp.dll).

Is there a way to tell ASP.NET to keep only .asp files?

+1


source to share


2 answers


one alternative is to create a virtual directory that can only execute .asp and no asp.net support.



+2


source


It looks like you have a wild card script mapping in your application config redirecting all requests to the aspnet_isapi.dll file. Is mapping .asp to asp.dll?



+1


source






More articles:


All Articles