Hi folks,
I have an application that does a security check on every page, asking if the user is logged in and changing the content to reflect their different status. This app uses an #include to minimize redundant code. Every page uses the same #include to add the file m_IdentityFunction.asp.
I have been asked to lock certain pages out entirely, so that users who aren't authorized get redirected to another page.
One way of doing this would be to Javascript to move the browser, but we don't want to create extra entries in the user's browser history.
The standard technique is to a response.redirect statement, but that must be placed before the <HTML> tag and therefore, before any #include statements. For maintainability, I would rather not copy the code to every page. Is there an easy way out?
Thanks in advance.
-Brian
I have an application that does a security check on every page, asking if the user is logged in and changing the content to reflect their different status. This app uses an #include to minimize redundant code. Every page uses the same #include to add the file m_IdentityFunction.asp.
I have been asked to lock certain pages out entirely, so that users who aren't authorized get redirected to another page.
One way of doing this would be to Javascript to move the browser, but we don't want to create extra entries in the user's browser history.
The standard technique is to a response.redirect statement, but that must be placed before the <HTML> tag and therefore, before any #include statements. For maintainability, I would rather not copy the code to every page. Is there an easy way out?
Thanks in advance.
-Brian