Hey all,
Recently at my work we deployed a custom authentication module written in C#. The module is developed for IIS 5.0 and IIS 6.0. There are a few problems when we try to deploy the module in IIS 6.0 which I really need your help and input.
In a few words, the module grabs the request injects the "WWW-Authenticate" header if its not there and switches HTTP status code to 401. This fakes IIS into show the login screen and let the user enter credentials. The credentials are checked against a database and if they are correct we cache them so we do not hit the database for each subsequent request the user makes. This worked well in IIS 5.0.
Most of the pages we want to authenticate are .html and .htm which contain frames. In IIS 6.0, because of the frames, subsequent requests are made (I was debugging and I was hitting my code for different pages) and in at least one request (always) the header is missing so based on the module design the he ...
Go to the complete details ...