I understand you can specify a login redirection page in your web config file if authentication is forms/passport.

Can you do that if you have windows authentication? Yes, I know you don't need a login page with windows authentication. What I'm after is a custom 401-3 error page which conforms to the theme of the application instead of the one found in ../iishelp/common/ directory.

Any ideas?

If I set the custom error page property in IIS to a page in my app, it will still not work, for the user will not have access to my app. Does this page need to be a part of another app perhaps?

TIA

You can build your own error pages and then map IIS to them in the console. Or you can specify the individual error pages in the web.config.

<configuration>
    <system.web>
        <customErrors mode="On" defaultRedirect="AppError.aspx">
            <error statusCode="404" redirect="notfound.aspx">
            <error statusCode="500" ... etc
        </customErrors>
    </system.web>
</configuration>

Thanks for the reply. Can this redirection page be a page of the app itself?

Are you asking if it can be one you created?

If you have an asp.net app, can the 401-3 error page be a page that is also a part of the app or does that page need to be not a part of the app so you have access to that page (even though you dont' have access to the app)

Typically, the custom error page is a page of the same application. When an error occurs on one page, it sends you to this error page. The page requests are separate so the error on the bad page *shouldn't* affect the run ability of the custom error page. If there IS an error on the error page, fortunately MS thought that thru and you don't end up in an error page loop. It just does what it can. Usually the error page will be a very simple page so it is less prone to errors.

Peter
-------------------------
Work smarter, not harder