Last post Jan 11, 2013 09:12 AM by Perkinsville
Jan 09, 2013 04:52 AM|kad24101986|LINK
My requirement is to an authenticate static HTML Page before they are viewed. To do so,
(a) I have written an HTTP Module. I check that if the request is for the HTML Page and the Session is not set, then redirect to the Login ASPX Page. Else, serve the HTML Page. I have also registered this module in Web.Config
(b) Next, I have written a Login ASPX Page that validates the user. If the user enter the correct username/password, I set the Session with User Id and redirect them to the HTML Page.
All of the above works well in the development environment, but once I deploy them to IIS, nothing works. I think that I am
P.S. : I use IIS 7.5. I need to deploy the app on two environments. One using Classic Mode and the other using Integrated Mode. In HTTP Module, I have written code in the AcquireRequestState event.
Jan 11, 2013 09:12 AM|Perkinsville|LINK
Without error codes or status Id's there is not much I can offer.
You may want to look at any preconditions on your module and make sure the application pool is configured in a way that will load the module.
Also, you can look in the Application event log for any errors, look in the IIS log or HTTP error logs for further clues.
I really like the Failed Request Trace capability in IIS 7+. Enable that and see if the module is being loaded or if there is an error logged. Here is a link to an article I wrote.