Msg#: 3298684 posted 12:27 am on Apr 1, 2007 (gmt 0)
Here my problem, I need to map static files though Asp.Net (on IIS 6, and IIS 5 if all possible). The gotcha is this will be on a shared hosting server so I am limited on access. The changes have to be limited to the specific website only, not server wide.
I have to put together a solution to protect the static files along with the dynamic content, based on login restrictions.
Msg#: 3298684 posted 2:17 am on Apr 1, 2007 (gmt 0)
I should of explained more that this be more of an addon to the site to add security to an existing application. Meaning I can not change how the current files are saved or current urls used in the application. What I need is how to set static files (html,jpg,gif,css) to be processed by asp.net process and not simply the IIS static file handler which by passes the asp.net process.
Msg#: 3298684 posted 5:57 am on Apr 1, 2007 (gmt 0)
Ok Here is what I am trying to implement. I have to protect old html (which I am not allowed to change or do anything with). I am not allowed to use file system permissions to limit access. It is require that it use a previously build login system, to limit the access.
All I am asking is there a way to configure IIS so that .html/.css/.jpg/.gif files can be mapped to the ASP.NET ISAPI extension, without going though the IIS Control panel. Basically what I am looking for is a way to upload a page, which when executed it will check the mappings and update them in the metabase so they are routed though asp.net instead of the default IIS static file handler, for the website in question, and not effect the rest of the websites on said webserver.
I know how to make and use HTTP handler to be used in asp.net, thats not the issue. Its just getting it into the asp.net pipeline in the first place.