Hi,
I have a requirement to protect all the static files like pdfs,html,doc etc from directly accessing just typing the url in the browser. for that reason, for each of the static file extension we have mapped the executable path as aspnet_isapi.dll which is protecting the static files from direct accessing and redirecting to login page. But some of the html files have SSI ( i.e. <!--#include virtual='test.html" -->) , but after changing the IIS setting from asp.dll to aspnet_isapi.dll, the include files are not being displayed.
So, my question is when .aspx extension has the same execuatble mapping path, i.e. it is getting protected from unauthenticated users and at the same time #include files are being displayed fine, then why it is not happening with .html extensions? is there any thing extra to be done for .html protection and working SSI properly.
Note:application is in 2.0 and server is windows 2003.
Go to the complete details ...