M
Matt MacDonald
Hi all,
Here is what I'm trying to accomplish. I need to secure every file in an
ASP.NET 2.0 website. From what I'm reading online, I should be able to do
this by registering the file extensions with the .net 2.0 ISAPI filter in
IIS and add an HTTPHandler item to my web.config. The problem I'm having is
that I can't seem to find a handler that will make the user log into the
site and then forward them back to the document they were trying to access
succesfully. If I add a wildcard filter to IIS that maps to the ISAPI
filter, then it works, but I can't update any of the files in the site using
VS2005. In 1.1 we would store protected documents in SQL and dynamically
stream them to the users after making them log in, but it seems that you
shouldn't have to do this if the new framework will do it for you.
Thanks,
Matt
Here is what I'm trying to accomplish. I need to secure every file in an
ASP.NET 2.0 website. From what I'm reading online, I should be able to do
this by registering the file extensions with the .net 2.0 ISAPI filter in
IIS and add an HTTPHandler item to my web.config. The problem I'm having is
that I can't seem to find a handler that will make the user log into the
site and then forward them back to the document they were trying to access
succesfully. If I add a wildcard filter to IIS that maps to the ISAPI
filter, then it works, but I can't update any of the files in the site using
VS2005. In 1.1 we would store protected documents in SQL and dynamically
stream them to the users after making them log in, but it seems that you
shouldn't have to do this if the new framework will do it for you.
Thanks,
Matt